summaryrefslogtreecommitdiff
path: root/docs/source/intro.rst
diff options
context:
space:
mode:
authorThomas Waldmann <tw AT waldmann-edv DOT de>2011-07-03 18:46:12 +0200
committerThomas Waldmann <tw AT waldmann-edv DOT de>2011-07-03 18:46:12 +0200
commit75166c8f974b98c60c131936b2d8933d6e9a1103 (patch)
tree70503a670e86ded6bf2b04be50be6a92425fff17 /docs/source/intro.rst
parent44e4db005f859f3213ae008988e01bf68b411aae (diff)
downloadxstatic-75166c8f974b98c60c131936b2d8933d6e9a1103.tar.gz
document xstatic packaging, some other doc fixes
Diffstat (limited to 'docs/source/intro.rst')
-rw-r--r--docs/source/intro.rst8
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/source/intro.rst b/docs/source/intro.rst
index 64ceffd..e87f2e6 100644
--- a/docs/source/intro.rst
+++ b/docs/source/intro.rst
@@ -25,7 +25,7 @@ they won't be required if you just want the files.
By having static files in packages, it is also easier to build virtual envs,
support linux/bsd/... distribution package maintainers and even windows installs
-using the same mechanisms.
+using the same mechanism.
Pros
====
@@ -38,11 +38,11 @@ Pros
your stuff into separate packages, so they don't need to
* outsource some work to other people. there are lots of people needing these
static packages, so you don't need to maintain them all yourself.
-* additionally to the files, you'll get some more-or-less metadata (like
- version info, name, CDN URLs (if any).
+* additionally to the files, you'll get some metadata (like version info, name,
+ CDN URLs (if any).
* we can use version number of the package to reflect the version of the packaged
static stuff and use the packaging system to require some specific version,
- or some specific minimum version.
+ or some specific minimum/maximum version.
* security updates are easier, the static file packages can be updated separately
from your main package.