Skip to content

Fix a few typos #710

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 3, 2016
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/scenarios/db.rst
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ Records

`Records <https://github.com/kennethreitz/records>`_ is minimalist SQL library,
designed for sending raw SQL queries to various databases. Data can be used
programatically, or exported to a number of useful data formats.
programmatically, or exported to a number of useful data formats.

.. code-block:: console

Expand Down
2 changes: 1 addition & 1 deletion docs/writing/structure.rst
Original file line number Diff line number Diff line change
Expand Up @@ -600,7 +600,7 @@ clearer and thus preferred.
This mechanism is useful for separating concerns and avoiding
external un-related logic 'polluting' the core logic of the function
or method. A good example of a piece of functionality that is better handled
with decoration is memoization or caching: you want to store the results of an
with decoration is memorization or caching: you want to store the results of an
expensive function in a table and use them directly instead of recomputing
them when they have already been computed. This is clearly not part
of the function logic.
Expand Down
4 changes: 2 additions & 2 deletions docs/writing/style.rst
Original file line number Diff line number Diff line change
Expand Up @@ -455,9 +455,9 @@ PEP 8
easy-to-read version of PEP 8 is also available at `pep8.org <http://pep8.org/>`_.

This is highly recommended reading. The entire Python community does their
best to adhere to the guidelines laidout within this document. Some project
best to adhere to the guidelines laid out within this document. Some project
may sway from it from time to time, while others may
`ammend its recommendations <http://docs.python-requests.org/en/master/dev/contributing/#kenneth-reitz-s-code-style>`_.
`amend its recommendations <http://docs.python-requests.org/en/master/dev/contributing/#kenneth-reitz-s-code-style>`_.

That being said, conforming your Python code to PEP 8 is generally a good
idea and helps make code more consistent when working on projects with other
Expand Down