diff --git a/docs/howto/custom-management-commands.txt b/docs/howto/custom-management-commands.txt index 8158890b83..2ab71e85ac 100644 --- a/docs/howto/custom-management-commands.txt +++ b/docs/howto/custom-management-commands.txt @@ -95,8 +95,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 diff --git a/docs/ref/contrib/admin/index.txt b/docs/ref/contrib/admin/index.txt index cfc15ed8f5..80673ce661 100644 --- a/docs/ref/contrib/admin/index.txt +++ b/docs/ref/contrib/admin/index.txt @@ -1207,7 +1207,7 @@ on whichever model contains the actual reference to the ``ManyToManyField``. Depending on your ``ModelAdmin`` definition, each many-to-many field in your model will be represented by a standard HTML ``