Improve docs (mostly spelling)

docs/en/installation/common-problems.md

@@ -58,19 +58,19 @@ every page on the site, if that's easier.
 ## I can see unparsed PHP output in my browser
 
 Please make sure all code inside `*.php` files is wrapped in classes. Due to the way `[api:ManifestBuilder]`
-includes all files with this extension, any **procedural code will be executed on every call**. Most common error here
+includes all files with this extension, any **procedural code will be executed on every call**. The most common error here
 is putting a test.php/phpinfo.php file in the document root. See [datamodel](/topics/datamodel) and [controllers](/topics/controller)
 for ways how to structure your code.
 
-Also, please check that you have PHP enabled on the webserver, and you're at least running PHP 5.1.
+Also, please check that you have PHP enabled on the webserver, and you're running PHP 5.1 or later.
 The web-based [SilverStripe installer](/installation) can help you with this.
 
 ## I've got file permission problems during installation
 
-The php installer needs to be able write files during installation, which should be restricted again afterwards. It
+The php installer needs to be able to write files during installation, which should be restricted again afterwards. It
 needs to create/have write-access to:
 
  * The main installation directory (for creating .htaccess file and assets directory)
  * The mysite folder (to create _config.php)
  * After the install, the assets directory is the only directory that needs write access.
- * Image thumbnails will not show in the CMS if permission is not given 
+ * Image thumbnails will not show in the CMS if permission is not given 

docs/en/installation/from-source.md

@@ -2,5 +2,5 @@
 
 The best way to install from source is to use [Composer](composer).
 
-The original instructions on this page have been removed, as they are obsolete and misleading.  Please use Composer
-instead.
+The original instructions on this page have been removed, as they were obsolete and misleading.  Please use Composer
+instead.

docs/en/installation/mac-osx.md

@@ -7,7 +7,7 @@ webserver on OSX we suggest using [MAMP](http://www.mamp.info/en/index.php) or u
 to manage your packages.
 
 If you want to use the default OSX PHP version then you will need to recompile your own versions of PHP with GD. Providing instructions
-for how to recompile PHP is beyond the scope of our documentation but try a online search.
+for how to recompile PHP is beyond the scope of our documentation but try an online search.
 
 ## Installing MAMP
 
@@ -34,4 +34,4 @@ won't come along.
 
 Open your web browser and go to `http://localhost:8888/silverstripe/`. Enter your database details - by default with MAMP its user `root` and password  `root` and select your account details. Click "Check Details".
 
-Once everything is sorted hit Install! and Voila you have SilverStripe installed 
+Once everything is sorted hit "Install!" and Voila,  you have SilverStripe installed 

docs/en/installation/server-requirements.md

@@ -36,7 +36,7 @@ Our web-based [PHP installer](/installation) can check if you meet the requireme
 
 ## Web server hardware requirements
 
-Hardware requirements vary widely depending on the traffic to your website, the complexity its logic (i.e., PHP), and its size (i.e., database.) By default, all pages are dynamic, and thus access both the database and execute PHP code to generate. SilverStripe can cache full pages and segments of templates to dramatically increase performance.
+Hardware requirements vary widely depending on the traffic to your website, the complexity of its logic (i.e., PHP), and its size (i.e., database.) By default, all pages are dynamic, and thus access both the database and execute PHP code to generate. SilverStripe can cache full pages and segments of templates to dramatically increase performance.
 
 A typical website page on a conservative single CPU machine (e.g., Intel 2Ghz) takes roughly 300ms to generate. This comfortably allows over a million page views per month. Caching and other optimisations can improve this by a factor of ten or even one hundred times. SilverStripe CMS can be used in multiple-server architectures to improve scalability and redunancy.
 

docs/en/installation/upgrading.md

@@ -1,13 +1,13 @@
 # Upgrading
 
-Usually an update or upgrade your SilverStripe installation just means 
+Usually an update or upgrade to your SilverStripe installation just means 
 overwriting files and updating your database-schema. 
 
 See our [upgrade notes and changelogs](/changelogs) for release-specific information.
 
 ## Process
 
-*  Check if any modules (e.g. blog or forum) in your installation are compatible and need to be upgraded as well
+*  Check if any modules (e.g. blog or forum) in your installation are incompatible and need to be upgraded as well
 *  Backup your database content
 *  Backup your webroot files
 *  Download the new release and uncompress it to a temporary folder
@@ -38,4 +38,4 @@ How easy will it be to update my project? It's a fair question, and sometimes a
 
 *  [Release Announcements](http://groups.google.com/group/silverstripe-announce/)
 *  [Blog posts about releases on silverstripe.org](http://silverstripe.org/blog/tag/release)
-* [/misc/release-process](Release Process)
+* [/misc/release-process](Release Process)

docs/en/installation/webserver.md

@@ -32,7 +32,7 @@ If the above steps don't work for any reason have a read of the [Common Problems
 
 ### Yaml
 
-For the reasons explained in [security](/topics/security) Yaml files are blocked by default by the .htaccess file
+For the reasons explained in [security](/topics/security), Yaml files are blocked by default by the .htaccess file
 provided by the SilverStripe installer module.
 
 To allow serving yaml files from a specific directory, add code like this to an .htaccess file in that directory

docs/en/installation/windows-manual-iis-7.md

@@ -218,7 +218,7 @@ Most of the time, it's caused by a loaded PHP extension that is broken.
 
 **Q: I get the error "HTTP Error 500.0 - Internal Server Error - C:\Program Files (x86)\PHP\php-cgi.exe - The FastCGI process exceeded configured request timeout"**
 
-**A:** A script is running for a long time, such as a unit test. To fix this, you'll need to increase the request timeout to a higher value in both IIS and PHP. Refer to the IIS FastCGI configuration documentation and PHP configuration parts of this document for where to change the appropriate values.
+**A:** A script has been running for a long time, such as a unit test. To fix this, you'll need to increase the request timeout to a higher value in both IIS and PHP. Refer to the IIS FastCGI configuration documentation and PHP configuration parts of this document for where to change the appropriate values.
 
 **Q: I cannot access SQL Server from a remote server, such as a development environment**
 

docs/en/misc/release-process.md

@@ -44,7 +44,7 @@ going into the *alpha* cycle. Preview releases are named *A.B.C-pr1* (and furthe
 
 So far, major releases have happened every couple of years. Most new releases are *minor version number* or *micro
 version number* increments.
-So far, we only had one major release, from the *1.x* to the *2.x* line.
+So far, we have had two major releases; from the *1.x* to the *2.x* line and from the *2.x* to the *3.x* line.
 
 ### Minor releases