diff options
| author | Ramiro Morales <cramm0@gmail.com> | 2011-02-14 15:02:02 +0000 |
|---|---|---|
| committer | Ramiro Morales <cramm0@gmail.com> | 2011-02-14 15:02:02 +0000 |
| commit | d7c2dcd5387e12828daf6fe4b852f2e894da79e8 (patch) | |
| tree | 3549560555a262fcdd1138aa6924f8d456058753 /docs/howto | |
| parent | 72e4a6865d36f8885e7a35ca8de8fe6d1ec3ff18 (diff) | |
Fixed a couple of documentation typos.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@15534 bcc190cf-cafb-0310-a4f2-bffc1f526a37
Diffstat (limited to 'docs/howto')
| -rw-r--r-- | docs/howto/custom-management-commands.txt | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/howto/custom-management-commands.txt b/docs/howto/custom-management-commands.txt index 1a8ba63a24..309e5c12ed 100644 --- a/docs/howto/custom-management-commands.txt +++ b/docs/howto/custom-management-commands.txt @@ -102,8 +102,8 @@ default options such as :djadminopt:`--verbosity` and :djadminopt:`--traceback`. The :meth:`BaseCommand.execute` method sets the hardcoded ``en-us`` locale because the commands shipped with Django perform several tasks - (for example, user-visible content and database population) that require - a system-neutral string language (for which we use ``en-us``). + (for example, user-facing content rendering and database population) that + require a system-neutral string language (for which we use ``en-us``). If your custom management command uses another locale, you should manually activate and deactivate it in your :meth:`~BaseCommand.handle` or |