Merge pull request #39 from jonathandion/feature/typos

Fixed some typos

docs/concepts/config.md

@@ -9,7 +9,7 @@ original_id: config
 
 <br />
 
-Renative configs are one of the most powerful feature of ReNative platform.
+Renative configs are one of the most powerful features of ReNative platform.
 
 Their format is `renative.*.json`
 

docs/guides/advanced-configuration.md

@@ -94,7 +94,7 @@ Every `rnv` job will generate unique build file in `./platformAssets/` folder.
 
 Naming convention of such file is `[APP_ID]_[PLATFORM].json`
 
-ie command `rnv run -p android -c helloworld` will genreate build file at:
+ie command `rnv run -p android -c helloworld` will generate build file at:
 
 `./platformBuilds/helloworld_android.json`
 
@@ -139,7 +139,7 @@ ie command `rnv run -p android -c helloworld` will generate build file at:
 
 `./platformAssets/renative.runtime.json`
 
-with followng value:
+with following value:
 
 ```json
 {
@@ -194,7 +194,7 @@ Following is the order of merges of various renative configs (if present) produc
 
 ## Dynamic Injectors
 
-You can inject varietry of different dynamic props via `renative.*.json` configs
+You can inject variety of different dynamic props via `renative.*.json` configs
 
 ```
 {{INJECTOR}}
@@ -235,7 +235,7 @@ Example:
 Currently supported runtime properties:
 
 - scheme
-- appConfing
+- appConfig
 - engine
 - localhost
 - timestamp

docs/overview/intro.md

@@ -74,7 +74,7 @@ RNV allows you to target over 15 different platforms.
 ---
 ## Tasks
 
-RNV is essentially and task runner. most of the execution is completed by tasks.
+RNV is essentially a task runner. Most of the execution is completed by tasks.
 
 ---
 ## App Code
@@ -93,7 +93,7 @@ More Info (Templates)
 ---
 ## File Extensions
 
-You can create highly sophisticated reusable multiplatofrm architecture by utilising powerful file extension system
+You can create highly sophisticated reusable multiplatform architecture by utilizing powerful file extension system
 
 ---
 ## Runtime