minor text and links fixes

README.md

@@ -1,7 +1,7 @@
 Meta-runner Power Pack
 ======================
 
-A collection of [Meta-runners](http://confluence.jetbrains.com/display/TCD9/Working+with+Meta-Runner) for TeamCity.
+A collection of [Meta-runners](http://confluence.jetbrains.com/display/TCD10/Working+with+Meta-Runner) for TeamCity.
 
 Available Meta-Runners
 ======================
@@ -36,15 +36,15 @@ Available Meta-Runners
 Installation Instructions
 =========================
 
-Each file called **MRPP_\<some text\>.xml** contains a definition of a single [Meta-runner](http://confluence.jetbrains.com/display/TCD9/Working+with+Meta-Runner).
+Each file called **MRPP_\<some text\>.xml** contains a definition of a single [Meta-runner](http://confluence.jetbrains.com/display/TCD10/Working+with+Meta-Runner).
 
-You can install a meta-runner directly via the file system or, since TeamCity 9.0 EAP1, using the TeamCity Web UI:
+You can install a meta-runner directly via the file system or, since TeamCity 9.0, using the TeamCity Web UI:
 
-- to install Meta-runner directly to the file system, take the Meta-runner definition file and put it into the [\<TeamCity Data Directory\>](http://confluence.jetbrains.com/display/TCD9/TeamCity+Data+Directory)/config/projects/\<Project ID\>/pluginData/metaRunners/ directory, where **\<Project ID\>** is the identifier of a project where you want to place the Meta-runner. If the **metaRunners** directory does not exist, it will be created. Once you place the file on the disk, TeamCity will detect it and load this Meta-runner; no server restart is required.
+- to install Meta-runner directly to the file system, take the Meta-runner definition file and put it into the [\<TeamCity Data Directory\>](http://confluence.jetbrains.com/display/TCD10/TeamCity+Data+Directory)/config/projects/\<Project ID\>/pluginData/metaRunners/ directory, where **\<Project ID\>** is the identifier of a project where you want to place the Meta-runner. If the **metaRunners** directory does not exist, it will be created. Once you place the file on the disk, TeamCity will detect it and load this Meta-runner; no server restart is required.
 
 - to install Meta-runner via the Web UI, go to the Project Settings page, select Meta-Runners from the list of settings on the left, click Upload Meta-Runner and select the Meta-runner definition file. Save you changes.
 
-If the Meta-runner is loaded succcessfully, you will see it listed on the Meta-Runners page for the project; if you have appropriate permissions, you can modify the definiton directly in the TeamCity UI. 
+If the Meta-runner is loaded successfully, you will see it listed on the Meta-Runners page for the project; if you have appropriate permissions, you can modify the definition directly in the TeamCity UI. 
 
 The runner is now available in the list of build runners on the build configuration Build Steps page and is represented as a native TeamCity runner with a convenient UI.
 
@@ -54,13 +54,13 @@ If you want a Meta-runner to be available to all of the projects, place it in th
 Troubleshooting
 ===============
 
-If you see the "Meta-Runner with specified name already exists" when attempting to upload a meta-runner via the UI or if
+If you see "Meta-Runner with specified name already exists" when attempting to upload a meta-runner via the UI, or if
 after placing the Meta-runner on the disk you see the following error in the TeamCity web interface:
 ``Meta-Runner with id '<some id>' was registered from path '<some path>\<meta runner file name>.xml'
 and cannot be overridden from path '<another path>\<meta runner file name>.xml'``
 
 it means that a Meta-runner with the same ID is already defined in another project. To fix it, you can either remove the old Meta-runner, or change the ID of the new one.
-The ID of the Meta-runner is the name of the file, so you can simply rename file. It makes sense to preserve prefix **MRPP_** so that you could understand where this Meta-runner came from.
+The ID of the Meta-runner is the name of the file, so you can simply rename the file. It makes sense to preserve prefix **MRPP_** so that you could understand where this Meta-runner came from.
 
 License
 =======