innov
/
django1
1
0
Fork 0
Code Issues Pull Requests 1 Projects Releases Wiki Activity

Removed unneeded right quotes in docs to fix spelling errors. 

A regression in pyenchant caused a problem:
https://github.com/rfk/pyenchant/issues/93
This commit is contained in:
Tim Graham 2017-07-18 08:24:49 -04:00
parent 33d453b2a7
commit 259875535b
4 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/intro/tutorial07.txt
View File

@ -328,8 +328,8 @@ when loading Django templates; it's a search path.
Just like the static files, we *could* have all our templates together, in Just like the static files, we *could* have all our templates together, in
one big templates directory, and it would work perfectly well. However, one big templates directory, and it would work perfectly well. However,
templates that belong to a particular application should be placed in that templates that belong to a particular application should be placed in that
application’s template directory (e.g. ``polls/templates``) rather than the application's template directory (e.g. ``polls/templates``) rather than the
project’s (``templates``). We'll discuss in more detail in the project's (``templates``). We'll discuss in more detail in the
:doc:`reusable apps tutorial </intro/reusable-apps>` *why* we do this. :doc:`reusable apps tutorial </intro/reusable-apps>` *why* we do this.
Now create a directory called ``admin`` inside ``templates``, and copy the Now create a directory called ``admin`` inside ``templates``, and copy the

2
docs/ref/class-based-views/index.txt
View File

@ -51,7 +51,7 @@ used by themselves or inherited from. They may not provide all the
capabilities required for projects, in which case there are Mixins which capabilities required for projects, in which case there are Mixins which
extend what base views can do. extend what base views can do.
Django’s generic views are built off of those base views, and were developed Django's generic views are built off of those base views, and were developed
as a shortcut for common usage patterns such as displaying the details of an as a shortcut for common usage patterns such as displaying the details of an
object. They take certain common idioms and patterns found in view object. They take certain common idioms and patterns found in view
development and abstract them so that you can quickly write common views of development and abstract them so that you can quickly write common views of

2
docs/topics/db/transactions.txt
View File

@ -390,7 +390,7 @@ run.
The solution is simple: instead of doing something during the atomic block The solution is simple: instead of doing something during the atomic block
(transaction) and then undoing it if the transaction fails, use (transaction) and then undoing it if the transaction fails, use
:func:`on_commit` to delay doing it in the first place until after the :func:`on_commit` to delay doing it in the first place until after the
transaction succeeds. It’s a lot easier to undo something you never did in the transaction succeeds. It's a lot easier to undo something you never did in the
first place! first place!
Low-level APIs Low-level APIs

2
docs/topics/performance.txt
View File

@ -235,7 +235,7 @@ Databases
Database optimization Database optimization
--------------------- ---------------------
Django’s database layer provides various ways to help developers get the best Django's database layer provides various ways to help developers get the best
performance from their databases. The :doc:`database optimization documentation performance from their databases. The :doc:`database optimization documentation
</topics/db/optimization>` gathers together links to the relevant </topics/db/optimization>` gathers together links to the relevant
documentation and adds various tips that outline the steps to take when documentation and adds various tips that outline the steps to take when