summaryrefslogtreecommitdiff
path: root/docs/howto/static-files
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:52:53 -0400
commit85c6a5a8c915a8d7e57b506f7dbfe864a78c2917 (patch)
treee3fa95d336911185009a8648fdcc37ee0f18f2e8 /docs/howto/static-files
parentff7d5e3a0bf3c81ca6289a93efb7e8a48b2460ef (diff)
[1.10.x] Normalized spelling of "Web server/page" in docs.
Backport of eb4d4376fc0f3958ef8e801434ef2bb61a07b56a from master
Diffstat (limited to 'docs/howto/static-files')
-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