changeset 1404:83d04b38b8fa

fixing some docs issues (syntax and semantics)
author Thomas Waldmann <tw AT waldmann-edv DOT de>
date Mon, 25 Jun 2012 12:24:49 +0200
parents 3bf3bc730b5d
children 0b947dbdffe8
files docs/admin/index.rst docs/devel/development.rst docs/intro/features.rst docs/intro/general.rst docs/user/rest.rst docs/user/search.rst
diffstat 6 files changed, 11 insertions(+), 10 deletions(-) [+]
line wrap: on
line diff
--- a/docs/admin/index.rst	Mon Jun 25 12:03:12 2012 +0200
+++ b/docs/admin/index.rst	Mon Jun 25 12:24:49 2012 +0200
@@ -137,7 +137,7 @@
 and also see results from the other wikis.
 
 Before you start, you must prepare your wiki configs. For example, for a company 
-that uses two wiki farms, such as ``Sales`` and ``Engineering``, Their respective 
+that uses two farm wikis, such as ``Sales`` and ``Engineering``, Their respective 
 wiki configs could look like:
 
 ``Sales``::
--- a/docs/devel/development.rst	Mon Jun 25 12:03:12 2012 +0200
+++ b/docs/devel/development.rst	Mon Jun 25 12:24:49 2012 +0200
@@ -29,7 +29,7 @@
 * http://bitbucket.org/thomaswaldmann/moin-2.0 - bitbucket mirror for your
   convenience, simplifying forking and contributing
 
-We use Mercurial DVCS and mercurial for distributed version control.
+We use Mercurial DVCS for distributed version control.
 
 If you are not using Mercurial, you can still submit patches.
 In that case, open an issue in the issue tracker and attach the patch there.
@@ -137,7 +137,7 @@
 * routing by name to some specific backend, like fstab / mount
 * indexing metadata and data + comfortable and fast index-based access,
   selection and search
-* protecting content by ACLs (Access Control Lists)
+* protecting items by ACLs (Access Control Lists)
 
 DOM based transformations
 -------------------------
@@ -151,7 +151,7 @@
 input and output mimetypes.
 
 For example, if the mimetype is `text/x-moin-wiki`, it will find that the input
-converter handling, this is the one defined in `converter.moinwiki_in`. It then
+converter handling this is the one defined in `converter.moinwiki_in`. It then
 feeds the data of this item into this converter. The converter parses this
 input and creates an in-memory `dom tree` representation from it.
 
--- a/docs/intro/features.rst	Mon Jun 25 12:03:12 2012 +0200
+++ b/docs/intro/features.rst	Mon Jun 25 12:24:49 2012 +0200
@@ -4,8 +4,9 @@
 
 Operating System Support
 ========================
-Moin is implemented in Python, a platform-independant language.
-It works on Linux, Mac OS X, Windows, FreeBSD and OSes compatible with these.
+Moin is implemented in Python, a platform-independent language.
+It works on Linux, Mac OS X, Windows, FreeBSD and other OSes that support
+Python.
 
 That said, Linux is the preferred and most tested deployment platform and
 will likely have fewer issues than, for example, Windows.
--- a/docs/intro/general.rst	Mon Jun 25 12:03:12 2012 +0200
+++ b/docs/intro/general.rst	Mon Jun 25 12:24:49 2012 +0200
@@ -42,12 +42,12 @@
 
 There are lots of wiki engines out there, making it hard to pick one.
 However, choosing wisely is important because you may have to live with 
-your choice for a long time and switching wiki engines is not easy.
+your choice for a long time because switching wiki engines is not easy.
 
 We won't list all of moin's features, because comparing feature lists
 is just not enough. Some features are best left unimplemented, 
 even if they sound great at first. In moin, you will find most
-important features in most major wiki engines. But still, you and your wiki
+important features like in most major wiki engines. But still, you and your wiki
 users might feel quite a different overall experience just because of a bunch
 of small, superficial differences. Of course the quality of some features'
 implementations can vary greatly. Thus, you have to
--- a/docs/user/rest.rst	Mon Jun 25 12:03:12 2012 +0200
+++ b/docs/user/rest.rst	Mon Jun 25 12:24:49 2012 +0200
@@ -372,7 +372,7 @@
 Literals Blocks
 ===============
 
-Literal blocks are used to show test as-it-is. i.e no markup processing is done within a literal block. 
+Literal blocks are used to show text as-it-is. i.e no markup processing is done within a literal block. 
 A minimum (1) indentation is required for the text block to be recognized as a literal block.
 
 **Markup**: ::
--- a/docs/user/search.rst	Mon Jun 25 12:03:12 2012 +0200
+++ b/docs/user/search.rst	Mon Jun 25 12:24:49 2012 +0200
@@ -12,7 +12,7 @@
 
 On the search results view you will get a bigger search query input field, 
 for example for refining your query, and you may also choose to additionally search
-in non-current item revisions. Sselecting that will search in all revisions.
+in non-current item revisions. Selecting that will search in all revisions.
 
 Simple search queries
 =====================