fixes in doc, build.md and readme.md (#191)

Author: grvsachdeva

BUILD.md

@@ -9,7 +9,7 @@ What you need to build the Coding with Chrome App
 In order to build the Coding with Chrome App, you only need to have Node.js/npm,
 git and Open JDK / Java JRE installed on your system.
 
-Each build is cross platform compatible. Which mean if you build the
+Each build is cross-platform compatible. Which mean if you build the
 Coding with Chrome App on Windows you could use the generated code
 `genfiles/chrome_app` folder in other platforms like Mac OS X as well.
 
@@ -62,7 +62,7 @@ cd coding-with-chrome
 
 ### Init / update submodules
 
-In some cases you need to init and update the submodules manually by:
+In some cases, you need to init and update the submodules manually by:
 
 ```bash
 git submodule init

README.md

@@ -29,7 +29,7 @@ core philosophies:
    * input languages (blockly, javascript, coffeescript)
    * output modules (turtle graphics, javascript output, connected robots)
    * Flexible UI where elements can be easily added, modified or removed
-   * Tutorial engine for self learning
+   * Tutorial engine for self-learning
 
 Licensing
 ----------

doc/ADDON.md

@@ -1,7 +1,7 @@
 Coding with Chrome - Addon
 ===========================
 
-Adding additional addons
+Adding additional add-ons
 -------------------------
 
 ### Create addon folder
@@ -10,10 +10,10 @@ For starting with an addon create a new folder under `src/addon/[Addon name]`.
 
 ### Addon rules
 
-To make sure addons are user friendly and not disruptive, there are some
+To make sure addons are user-friendly and not disruptive, there are some
 general rules.
 
-* The addon needs to be activated by the user an can not be auto-enabled.
+* The addon needs to be activated by the user and cannot be auto-enabled.
 * The addon should not change any core functionality.
 
 ### Events

doc/ARCHITECTURE.md

@@ -101,7 +101,7 @@ preparations to execute the user generated code.
 
 ### Runner
 
-The runner is used if a hardware communication between the user generated code
+The runner is used if a hardware communication between the user-generated code
 and the serial, Bluetooth or USB interface is needed.
 The code will be executed in the sandbox as well, but will have limited access
 to the internal apis over the runner framekwork / runner api.

doc/BUILD_MAC_APP.md

@@ -12,7 +12,7 @@ using this document.
 Build the core files
 ---------------------
 
-In order to build the actual app you need first to build all core files.
+In order to build the actual app, you need first to build all core files.
 This step is normally needed only once and after an update of the core files.
 This could be done with the following command:
 
@@ -40,7 +40,7 @@ npm run publish:nw_app-mac
 ```
 
 The build version will be compiled in the `/dist/binary/osx64` directory,
-together with all required packages and files.
+together with all the required packages and files.
 
 ### Launch the app
 

doc/BUILD_RELEASE_CHECKLIST.md

@@ -4,23 +4,23 @@ Coding with Chrome - Release checklist
 <img src="../static_files/images/cwc_logo.png" align="right">
 
 These following actions needs to be performed before each release.
-This makes sure that an release is not breaking any major function.
+This makes sure that a release is not breaking any major function.
 
 Automated Tests
 ----------------
 
-Most of the general errors are catched by the automated tests.
+Most of the general errors are caught by the automated tests.
 But it's not possible to have an 100% test coverage, so these tests will not
 catch all race conditions.
 
-- [ ] Run "npm run test" and check if any test fail
+- [ ] Run "npm run test" and check if any test fails
 
 - [ ] Check <https://travis-ci.org/google/coding-with-chrome>
 
 - [ ] Check <https://codeclimate.com/github/google/coding-with-chrome>
 
 - [ ] Check coverage report under /coverage. The overall status should be
-  at least 55%, if less additional tests needs to be added.
+  at least 55%, if less additional tests need to be added.
 
 UI Tests
 ---------

doc/DEBUG.md

@@ -1,7 +1,7 @@
 Coding with Chrome - Debugging
 ===============================
 
-This document covers debugging informations and technique's for the
+This document covers debugging information and technique's for the
 Coding with Chrome editor.
 
 General options
@@ -33,7 +33,7 @@ npm run debug
 
 ### Sync latest files and dependencies
 
-In some cases you need to update the dependencies to the latest version to
+In some cases, you need to update the dependencies to the latest version to
 get everything working. This can be done with the following command:
 
 ```bash
@@ -53,7 +53,7 @@ Live debugging
 ---------------
 
 The following methods will help you to debug certain functions or parts without
-the need to recompile the hole source code.
+the need to recompile the whole source code.
 
 ### Using dist/chrome_os/js/debug.js
 
@@ -63,7 +63,7 @@ change function without the need of recompile everything.
 Just overwrite your function in the `dist/chrome_os/js/debug.js` file and reload
 the application to see your change in action.
 
-In some cases it could be that you need to insert the hole object definition
+In some cases, it could be that you need to insert the whole object definition
 here and not only parts of it.
 
 Original definition:
@@ -92,7 +92,7 @@ recompile the code.**
 Instead of overwriting definitions in the `dist/chrome_os/js/debug.js` file you
 could directly replace them in the `dist/chrome_os/js/cwc_ui.js` file.
 
-Please keep in mind that this file contains optimized code, so its not really
+Please keep in mind that this file contains optimized code, so it's not really
 readable but this will also avoid to re-compile the code to test something.
 
 Original `dist/chrome_os/js/cwc_ui.js`:

doc/DEVELOPMENT.md

@@ -21,8 +21,8 @@ You might also check Enable CSS Source Maps.
 
 ### Running the debug mode
 
-During development you should only use the debug mode, which provides additional
-informations and pre-checks over:
+During development, you should only use the debug mode, which provides additional
+information and pre-checks over:
 
 ```bash
 npm run debug
@@ -34,7 +34,7 @@ Other options
 ### Rebuild the app
 
 If you change something in the source code, you need to re-compile it.
-After this you only need to reload the Chrome App to see your change in action.
+After this, you only need to reload the Chrome App to see your change in action.
 
 ### Update dependencies
 
@@ -44,12 +44,12 @@ Run the following command to update the dependencies to the latest version:
 npm run sync
 ```
 
-After this you only need to reload the Chrome App to see your change in action.
+After this, you only need to reload the Chrome App to see your change in action.
 
 ### Google Drive support (experimental)
 
 Since this feature is experimental, although problems are unlikely we can not
-guarantee this code is error free. Please make sure that you back up your
+guarantee this code is error-free. Please make sure that you back up your
 Google Drive data, or only use test accounts without critical files or data.
 
 See: <https://developer.chrome.com/apps/app_identity>

doc/I18N.md

@@ -4,7 +4,7 @@ Coding with Chrome - i18n translation
 Adding additional language support
 -----------------------------------
 
-### Create language folder
+### Create a language folder
 
 If your language is currently not supported, create a new folder under
 `locales/[language code]/`.
@@ -75,9 +75,9 @@ the different type of text.
 (Skip the deprecated `locales/eng/translation.js` file!)
 
 Please make sure that you only add translated text into this new file.
-It also fine to start with a few line and adding the rest later.
+It also fine to start with a few lines and adding the rest later.
 
-If the new file is ready, create an pull request under the following URL:
+If the new file is ready, create a pull request under the following URL:
 <https://github.com/google/coding-with-chrome/pulls>
 
 Translation Key Format
@@ -124,7 +124,7 @@ Missing translations
 
 If you miss the translation for certain UI parts, please submit pull request to
 add them.
-All translations are using an KEY for the translation and maybe separates files
+All translations are using a KEY for the translation and maybe separates files
 like **locales/deu/welcome_screen.js**.
 
 ### In JavaScript files

doc/MODES.md

@@ -14,7 +14,7 @@ Workflow
    for the file type (cwc.file.Type).
 
 3. The modder (cwc.mode.Modder) build the UI, loads the content and
-   defines the used renderer according the mode config (cwc.mode.ConfigData).
+   defines the used renderer according to the mode config (cwc.mode.ConfigData).
 
 Add a new file_type
 --------------------