summaryrefslogtreecommitdiff
path: root/docs/howto/static-files/deployment.txt
diff options
context:
space:
mode:
Diffstat (limited to 'docs/howto/static-files/deployment.txt')
-rw-r--r--docs/howto/static-files/deployment.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/howto/static-files/deployment.txt b/docs/howto/static-files/deployment.txt
index c1421d8244..49ac738b29 100644
--- a/docs/howto/static-files/deployment.txt
+++ b/docs/howto/static-files/deployment.txt
@@ -44,7 +44,7 @@ multiple web servers.
Serving static files from a dedicated server
--------------------------------------------
-Most larger Django sites use a separate Web server -- i.e., one that's not also
+Most larger Django sites use a separate web server -- i.e., one that's not also
running Django -- for serving static files. This server often runs a different
type of web server -- faster but less full-featured. Some common choices are:
@@ -75,7 +75,7 @@ Serving static files from a cloud service or CDN
Another common tactic is to serve static files from a cloud storage provider
like Amazon's S3 and/or a CDN (content delivery network). This lets you
ignore the problems of serving static files and can often make for
-faster-loading Web pages (especially when using a CDN).
+faster-loading web pages (especially when using a CDN).
When using these services, the basic workflow would look a bit like the above,
except that instead of using ``rsync`` to transfer your static files to the