summaryrefslogtreecommitdiff
path: root/docs/topics/settings.txt
diff options
context:
space:
mode:
authorDavid Smith <smithdc@gmail.com>2021-07-23 07:48:16 +0100
committerMariusz Felisiak <felisiak.mariusz@gmail.com>2021-07-29 06:24:12 +0200
commit1024b5e74a7166313ad4e4975a15e90dccd3ec5f (patch)
tree05d75177f183de5e3c58dbf25a3f71ff4a5c820a /docs/topics/settings.txt
parentacde91745656a852a15db7611c08cabf93bb735b (diff)
Fixed 32956 -- Lowercased spelling of "web" and "web framework" where appropriate.
Diffstat (limited to 'docs/topics/settings.txt')
-rw-r--r--docs/topics/settings.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/topics/settings.txt b/docs/topics/settings.txt
index 1e5f48f50d..e7d9d0c772 100644
--- a/docs/topics/settings.txt
+++ b/docs/topics/settings.txt
@@ -148,7 +148,7 @@ Security
Because a settings file contains sensitive information, such as the database
password, you should make every attempt to limit access to it. For example,
-change its file permissions so that only you and your Web server's user can
+change its file permissions so that only you and your web server's user can
read it. This is especially important in a shared-hosting environment.
Available settings
@@ -287,7 +287,7 @@ settings and populate Django's application registry. For example::
from myapp import models
Note that calling ``django.setup()`` is only necessary if your code is truly
-standalone. When invoked by your Web server, or through :doc:`django-admin
+standalone. When invoked by your web server, or through :doc:`django-admin
</ref/django-admin>`, Django will handle this for you.
.. admonition:: ``django.setup()`` may only be called once.