summaryrefslogtreecommitdiff
path: root/docs/howto/static-files/deployment.txt
diff options
context:
space:
mode:
authorTim Graham <timograham@gmail.com>2016-09-29 19:51:59 -0400
committerTim Graham <timograham@gmail.com>2016-09-29 19:51:59 -0400
commiteb4d4376fc0f3958ef8e801434ef2bb61a07b56a (patch)
tree9624bd3ad4daa04f6ac255c79927a39349dc57ec /docs/howto/static-files/deployment.txt
parenta09c058918f85949fd4c003e7ae62869f4559bd3 (diff)
Normalized spelling of "Web server/page" in docs.
Diffstat (limited to 'docs/howto/static-files/deployment.txt')
-rw-r--r--docs/howto/static-files/deployment.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/howto/static-files/deployment.txt b/docs/howto/static-files/deployment.txt
index 805e799eaa..6c116f816f 100644
--- a/docs/howto/static-files/deployment.txt
+++ b/docs/howto/static-files/deployment.txt
@@ -117,7 +117,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 webpages (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