diff options
| author | Tim Graham <timograham@gmail.com> | 2017-07-18 08:24:49 -0400 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2017-07-18 08:24:49 -0400 |
| commit | 259875535b1fb4238eefbe9d50c761d0702a1ce2 (patch) | |
| tree | d73cc75c22d76cb0f1951cc582043fc98b5a0004 /docs | |
| parent | 33d453b2a713ad2557b6ba31a903c142263641ed (diff) | |
Removed unneeded right quotes in docs to fix spelling errors.
A regression in pyenchant caused a problem:
https://github.com/rfk/pyenchant/issues/93
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/intro/tutorial07.txt | 4 | ||||
| -rw-r--r-- | docs/ref/class-based-views/index.txt | 2 | ||||
| -rw-r--r-- | docs/topics/db/transactions.txt | 2 | ||||
| -rw-r--r-- | docs/topics/performance.txt | 2 |
4 files changed, 5 insertions, 5 deletions
diff --git a/docs/intro/tutorial07.txt b/docs/intro/tutorial07.txt index 7dd0f42e22..04f2fa7060 100644 --- a/docs/intro/tutorial07.txt +++ b/docs/intro/tutorial07.txt @@ -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 one big templates directory, and it would work perfectly well. However, templates that belong to a particular application should be placed in that - application’s template directory (e.g. ``polls/templates``) rather than the - project’s (``templates``). We'll discuss in more detail in the + application's template directory (e.g. ``polls/templates``) rather than the + project's (``templates``). We'll discuss in more detail in the :doc:`reusable apps tutorial </intro/reusable-apps>` *why* we do this. Now create a directory called ``admin`` inside ``templates``, and copy the diff --git a/docs/ref/class-based-views/index.txt b/docs/ref/class-based-views/index.txt index 5670849562..17bd5315ff 100644 --- a/docs/ref/class-based-views/index.txt +++ b/docs/ref/class-based-views/index.txt @@ -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 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 object. They take certain common idioms and patterns found in view development and abstract them so that you can quickly write common views of diff --git a/docs/topics/db/transactions.txt b/docs/topics/db/transactions.txt index 0f028dd343..7ada3948ce 100644 --- a/docs/topics/db/transactions.txt +++ b/docs/topics/db/transactions.txt @@ -390,7 +390,7 @@ run. The solution is simple: instead of doing something during the atomic block (transaction) and then undoing it if the transaction fails, use :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! Low-level APIs diff --git a/docs/topics/performance.txt b/docs/topics/performance.txt index 1306a28c8e..74794415b7 100644 --- a/docs/topics/performance.txt +++ b/docs/topics/performance.txt @@ -235,7 +235,7 @@ Databases 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 </topics/db/optimization>` gathers together links to the relevant documentation and adds various tips that outline the steps to take when |