From d8fecb4d9942d3fbaecbbac0bbe0677a6b88d445 Mon Sep 17 00:00:00 2001
From: Alexey Pyltsyn <lex61rus@gmail.com>
Date: Fri, 4 Oct 2019 12:39:06 +0300
Subject: [PATCH] Improve docs

---
 docs/cookbook/tab-view-ng.md                  |   4 +-
 .../accessing-native-apis-with-javascript.md  |   2 +-
 docs/core-concepts/angular-data-binding.md    |   2 +-
 docs/core-concepts/angular-navigation.md      | 112 +++++++++---------
 docs/core-concepts/data-binding.md            |  30 ++---
 docs/core-concepts/error-handling.md          |  16 +--
 docs/core-concepts/memory-management.md       |   2 +-
 docs/core-concepts/plugins.md                 |   2 +-
 docs/core-concepts/properties.md              |   8 +-
 docs/core-concepts/utils.md                   |  72 +++++------
 .../plugins/Android-Plugins-Infrastructure.md |   4 +-
 docs/plugins/implementing-core-theme.md       |   4 +-
 docs/plugins/ui-plugin-custom.md              |   4 +-
 .../user-guide/enterprise-auth/openid.md      |   2 +-
 .../user-guide/enterprise-auth/saml.md        |   2 +-
 docs/tooling/angular-cli.md                   |   2 +-
 docs/tooling/debugging/chrome-devtools.md     |   2 +-
 .../continuous-integration.md                 |   2 +-
 .../end-to-end-testing/customization.md       |   2 +-
 .../end-to-end-testing/getting-started.md     |   6 +-
 20 files changed, 141 insertions(+), 139 deletions(-)

diff --git a/docs/cookbook/tab-view-ng.md b/docs/cookbook/tab-view-ng.md
index f14980e50..5c139f9e5 100644
--- a/docs/cookbook/tab-view-ng.md
+++ b/docs/cookbook/tab-view-ng.md
@@ -112,8 +112,8 @@ export class DataItem {
 }
 
 @Component({
-	selector: "tab-view-test",
-	templateUrl: "tab-view-test.html"
+    selector: "tab-view-test",
+    templateUrl: "tab-view-test.html"
 })
 export class TabViewTest {
     public items: Array<DataItem>;
diff --git a/docs/core-concepts/accessing-native-apis-with-javascript.md b/docs/core-concepts/accessing-native-apis-with-javascript.md
index e8315c20a..1bc4efa56 100644
--- a/docs/core-concepts/accessing-native-apis-with-javascript.md
+++ b/docs/core-concepts/accessing-native-apis-with-javascript.md
@@ -149,7 +149,7 @@ let array = new NSMutableArray();
 array.addObject(new NSObject());
 ```
 
-This snippet creates an instance of `NSMutableArray` and adds an object to it using the `addObject(object)` method. Here is what happens behind the curtains: the `new NSMutableArray()` call is translated to a `[[NSMutableArray alloc] init]` call by the iOS Runtime. This instance is then wrapped in a JavaScript object and stored in the `array` variable. It contains all public properties and methods exposed by `NSMutableArray` (and its base classes) in its prototype chain. While the `addObject(object)` call is straightforward, calling Objective-C methods with more arguments follows several simple rules that define how Objective-C selectors are mapped to JavaScript functions. Let's consider the following `NSMutableArray` selector: `replaceObjectsInRange:withObjectsFromArray:range:`. In JavaScript it is represented by the following function: `replaceObjectsInRangeWithObjectsFromArrayRange(objectsToRange, souceArray, sourceRange)` (argument names are arbitrary). Note that the function name is generated by appending the names of the arguments as defined by the Objective-C selector by starting with a small letter for the first argument and appending each subsequent with a capital letter.
+This snippet creates an instance of `NSMutableArray` and adds an object to it using the `addObject(object)` method. Here is what happens behind the curtains: the `new NSMutableArray()` call is translated to a `[[NSMutableArray alloc] init]` call by the iOS Runtime. This instance is then wrapped in a JavaScript object and stored in the `array` variable. It contains all public properties and methods exposed by `NSMutableArray` (and its base classes) in its prototype chain. While the `addObject(object)` call is straightforward, calling Objective-C methods with more arguments follows several simple rules that define how Objective-C selectors are mapped to JavaScript functions. Let's consider the following `NSMutableArray` selector: `replaceObjectsInRange:withObjectsFromArray:range:`. In JavaScript it is represented by the following function: `replaceObjectsInRangeWithObjectsFromArrayRange(objectsToRange, sourceArray, sourceRange)` (argument names are arbitrary). Note that the function name is generated by appending the names of the arguments as defined by the Objective-C selector by starting with a small letter for the first argument and appending each subsequent with a capital letter.
 
 #### NSDictionary
 
diff --git a/docs/core-concepts/angular-data-binding.md b/docs/core-concepts/angular-data-binding.md
index ccfba9204..366d02c9e 100644
--- a/docs/core-concepts/angular-data-binding.md
+++ b/docs/core-concepts/angular-data-binding.md
@@ -46,7 +46,7 @@ onButtonTap(args: EventData) {
 
 > Before we can use the ngModel directive in a two-way data binding, we must import the **NativeScriptFormsModule** and add it to the Angular module's imports list:
 > ```typescript
-import {NativeScriptFormsModule} from "nativescript-angular/forms"
+import { NativeScriptFormsModule } from "nativescript-angular/forms"
 @NgModule({
 	imports: [
 		NativeScriptModule,
diff --git a/docs/core-concepts/angular-navigation.md b/docs/core-concepts/angular-navigation.md
index 5a0b83b1e..9d854e136 100644
--- a/docs/core-concepts/angular-navigation.md
+++ b/docs/core-concepts/angular-navigation.md
@@ -67,8 +67,8 @@ import { RouterExtensions } from "nativescript-angular/router";
 })
 export class MainComponent {
 
-	constructor(private routerExtensions: RouterExtensions) {
-	}
+    constructor(private routerExtensions: RouterExtensions) {
+    }
 }
 ```
 
@@ -240,17 +240,17 @@ export class AppComponent { }
 import { Component, OnInit } from "@angular/core";
 
 @Component({
-	selector: "Hub",
-	templateUrl: "./hub.component.html",
-	styleUrls: ['./hub.component.css']
+    selector: "Hub",
+    templateUrl: "./hub.component.html",
+    styleUrls: ['./hub.component.css']
 })
 export class HubComponent implements OnInit {
 
-	constructor() {
-	}
+    constructor() {
+    }
 
-	ngOnInit(): void {
-	}
+    ngOnInit(): void {
+    }
 }
 ```
 ```hub.component.html
@@ -268,21 +268,21 @@ import { Component, OnInit } from "@angular/core";
 import { Location } from "@angular/common";
 
 @Component({
-	selector: "Featured",
-	templateUrl: "./featured.component.html",
-	styleUrls: ['./featured.component.css']
+    selector: "Featured",
+    templateUrl: "./featured.component.html",
+    styleUrls: ['./featured.component.css']
 })
 export class FeaturedComponent implements OnInit {
 
-	constructor(private location: Location) {
-	}
+    constructor(private location: Location) {
+    }
 
-	ngOnInit(): void {
-	}
+    ngOnInit(): void {
+    }
 
-	goBack(): void {
-		this.location.back();
-	}
+    goBack(): void {
+        this.location.back();
+    }
 }
 ```
 ```featured.component.html
@@ -372,17 +372,17 @@ import { Component, OnInit } from "@angular/core";
 import { RouterExtensions } from "nativescript-angular/router";
 
 @Component({
-	selector: "Featured",
-	templateUrl: "./featured.component.html",
-	styleUrls: ['./featured.component.css']
+    selector: "Featured",
+    templateUrl: "./featured.component.html",
+    styleUrls: ['./featured.component.css']
 })
 export class FeaturedComponent implements OnInit {
 
-	constructor(private routerExtensions: RouterExtensions) {
-	}
+    constructor(private routerExtensions: RouterExtensions) {
+    }
 
-	ngOnInit(): void {
-	}
+    ngOnInit(): void {
+    }
 }
 ```
 ```featured.component.html
@@ -398,17 +398,17 @@ export class FeaturedComponent implements OnInit {
 import { Component, OnInit } from "@angular/core";
 
 @Component({
-	selector: "Item",
-	templateUrl: "./item.component.html",
-	styleUrls: ['./item.component.css']
+    selector: "Item",
+    templateUrl: "./item.component.html",
+    styleUrls: ['./item.component.css']
 })
 export class ItemComponent implements OnInit {
 
-	constructor() {
-	}
+    constructor() {
+    }
 
-	ngOnInit(): void {
-	}
+    ngOnInit(): void {
+    }
 }
 ```
 ```item.component.html
@@ -434,21 +434,21 @@ import { Component, OnInit } from "@angular/core";
 import { RouterExtensions } from "nativescript-angular/router";
 
 @Component({
-	selector: "Item",
-	templateUrl: "./item.component.html",
-	styleUrls: ['./item.component.css']
+    selector: "Item",
+    templateUrl: "./item.component.html",
+    styleUrls: ['./item.component.css']
 })
 export class ItemComponent implements OnInit {
 
-	constructor(private routerExtensions: RouterExtensions) {
-	}
+    constructor(private routerExtensions: RouterExtensions) {
+    }
 
-	ngOnInit(): void {
-	}
+    ngOnInit(): void {
+    }
 
-	goBack(): void {
-		this.routerExtensions.back();
-	}
+    goBack(): void {
+        this.routerExtensions.back();
+    }
 }
 ```
 ```item.component.html
@@ -561,11 +561,11 @@ import { Component, OnInit } from "@angular/core";
 })
 export class HubComponent implements OnInit {
 
-	constructor() {
-	}
+    constructor() {
+    }
 
-	ngOnInit(): void {
-	}
+    ngOnInit(): void {
+    }
 }
 ```
 ```hub.component.html
@@ -620,7 +620,7 @@ The `TabView` component enables the user to arbitrarily navigate between several
 
 ![navigation-diagram-ng-tab](../img/navigation/navigation-diagram-ng-tab.png?raw=true)
 
-The `BottomNavigation` container provides its lateral navigation logic automatically by providing the user with tabs which they can select. To set up a `BottomNavigation` you need to simply declare the UI of each container via a `TabItemContent` and set the title and icon via coresponding `tabStripItem` (details on the basic structure [here](http://localhost:9192/angular/ui/ng-ui-widgets/bottom-navigation#usage)). Each separate UI container is represented by the `TabContentItem` component. As with other containers, you can enable forward and backward navigation inside each of them by embedding a `page-router-outlet` in it. In this case we need to use three sibling outlets. The way to do this with the Angular router is to use [named outlets](https://angular.io/guide/router#displaying-multiple-routes-in-named-outlets). Each of our outlets will be named with the name of the feature that it represents.
+The `BottomNavigation` container provides its lateral navigation logic automatically by providing the user with tabs which they can select. To set up a `BottomNavigation` you need to simply declare the UI of each container via a `TabItemContent` and set the title and icon via corresponding `tabStripItem` (details on the basic structure [here](http://localhost:9192/angular/ui/ng-ui-widgets/bottom-navigation#usage)). Each separate UI container is represented by the `TabContentItem` component. As with other containers, you can enable forward and backward navigation inside each of them by embedding a `page-router-outlet` in it. In this case we need to use three sibling outlets. The way to do this with the Angular router is to use [named outlets](https://angular.io/guide/router#displaying-multiple-routes-in-named-outlets). Each of our outlets will be named with the name of the feature that it represents.
 
 The `BottomNavigation` widget also provides two important features connected to lateral navigation:
 
@@ -712,7 +712,7 @@ export class AppComponent {
 ```app.component.html
 <BottomNavigation selectedIndex="1">
 
-    <!-- The bottom tab UI is created via TabStrip (the containier) and TabStripItem (for each tab)-->
+    <!-- The bottom tab UI is created via TabStrip (the container) and TabStripItem (for each tab)-->
     <TabStrip>
         <TabStripItem>
             <Label text="Home"></Label>
@@ -747,17 +747,17 @@ export class AppComponent {
 import { Component, OnInit } from "@angular/core";
 
 @Component({
-	selector: "Featured",
-	templateUrl: "./featured.component.html",
-	styleUrls: ['./featured.component.css']
+    selector: "Featured",
+    templateUrl: "./featured.component.html",
+    styleUrls: ['./featured.component.css']
 })
 export class FeaturedComponent implements OnInit {
 
-	constructor() {
-	}
+    constructor() {
+    }
 
-	ngOnInit(): void {
-	}
+    ngOnInit(): void {
+    }
 }
 ```
 ```featured.component.html
diff --git a/docs/core-concepts/data-binding.md b/docs/core-concepts/data-binding.md
index 5c083dd18..83e622bd0 100644
--- a/docs/core-concepts/data-binding.md
+++ b/docs/core-concepts/data-binding.md
@@ -240,22 +240,22 @@ Another common case in working with bindings is requesting access to the parent
 _Example 4: Creating ListView child items based on the itemTemplate._
 ``` XML
 <Page navigatingTo="onNavigatingTo" xmlns="http://schemas.nativescript.org/tns.xsd">
-	<GridLayout rows="*" >{%raw%}
-		<ListView items="{{ items }}">
-			<!--Describing how the element will look like-->
-			<ListView.itemTemplate>
-				<GridLayout columns="auto, *">
-					<Label text="{{ $value }}" col="0"/>
-					<!--The TextField has a different bindingCotnext from the ListView, but has to use its properties. Thus the parents['ListView'] has to be used.-->
-					<!-- Parent binding to a string property -->
+    <GridLayout rows="*" >{%raw%}
+        <ListView items="{{ items }}">
+            <!--Describing how the element will look like-->
+            <ListView.itemTemplate>
+                <GridLayout columns="auto, *">
+                    <Label text="{{ $value }}" col="0"/>
+                    <!--The TextField has a different bindingCotnext from the ListView, but has to use its properties. Thus the parents['ListView'] has to be used.-->
+                    <!-- Parent binding to a string property -->
                     <TextField text="{{ $parents['ListView'].test, $parents['ListView'].test }}" col="1"/>
 
                     <!-- Parent binding to a method onTap -->
                     <Button text="Tap me" tap="{{ $parents['ListView'].onTap,  $parents['ListView'].onTap }}" />
-				</GridLayout>
-			</ListView.itemTemplate>
-		</ListView>
-	{%endraw%}</GridLayout>
+                </GridLayout>
+            </ListView.itemTemplate>
+        </ListView>
+    {%endraw%}</GridLayout>
 </Page>
 ```
 ``` JavaScript
@@ -301,9 +301,9 @@ You can create a custom expression for bindings. Custom expressions could help i
 
 ``` XML
 <Page xmlns="http://schemas.nativescript.org/tns.xsd">
-	<StackLayout>{%raw%}
-		<TextField text="{{ sourceProperty, sourceProperty + ' some static text' }}" />
-{%endraw%}	</StackLayout>
+    <StackLayout>{%raw%}
+        <TextField text="{{ sourceProperty, sourceProperty + ' some static text' }}" />
+    {%endraw%}</StackLayout>
 </Page>
 ```
 
diff --git a/docs/core-concepts/error-handling.md b/docs/core-concepts/error-handling.md
index 685d27f57..ee8b5539c 100644
--- a/docs/core-concepts/error-handling.md
+++ b/docs/core-concepts/error-handling.md
@@ -43,26 +43,28 @@ This API also introduces a technique, which allows the developers to define cust
 
 Example:
 
-```
+```javascript
 import "./bundle-config";
 import * as application from "tns-core-modules/application";
-import * as traceModule from "tns-core-modules/trace"
+import * as traceModule from "tns-core-modules/trace";
+
 const errorHandler: traceModule.ErrorHandler = {
-    handlerError(err){
-        //option 1 (development) - throw the error
+    handlerError(err) {
+        // Option 1 (development) - throw the error
         throw err;
 
-        //option 2 (development) - logging the error via write method provided from trace module
+        // Option 2 (development) - logging the error via write method provided from trace module
         traceModule.write(err, "unhandled-error", type.error);
 
-        //(production) - custom functionality for error handling
-        //reportToAnalytics(err)
+        // (production) - custom functionality for error handling
+        // reportToAnalytics(err)
     }
 }
 
 traceModule.setErrorHandler(errorHandler)
 application.run({ moduleName: 'app-root' });
 ```
+
 The example shows how to define a custom handler and three possible options for handling the error via [trace]({%slug trace%}) module or while using custom functionality.
 
 Further info about the error handing in NativeScript can be found [here](https://github.com/NativeScript/NativeScript/blob/master/HandlingErrors.md).
diff --git a/docs/core-concepts/memory-management.md b/docs/core-concepts/memory-management.md
index 8d1f80ad0..2fdac117c 100644
--- a/docs/core-concepts/memory-management.md
+++ b/docs/core-concepts/memory-management.md
@@ -141,7 +141,7 @@ Unlike iOS, both the Java and JavaScript in the Android runtime are managed. The
 Memory leaks are rare. If there is a pool of unreachable splices from either Java or JavaScript, at some point the V8 GC will notify the JavaScript instances that they are marked for collection, then the reference to the Java counterpart will be made weak. Then the next Android VM GC will collect the Java instances and the V8 GC after that will collect the JavaScript instances (because the Java counterparts will be dead).
 
 #### Half-Dead Splice
-Since collection is driven by the garbage collectors it is possible to hold a weak reference to the JavaScript instance of a splice. After a V8 GC, the splice can make the reference to the Java instance weak allowing the Android VM GC to collect it. Then, if before the next V8 GC the JavaScript instance is obtained from the weak reference and its methods are called, it will result in accessinga a half-dead splice (since the Java counterpart is dead already). The error reported by the runtime points out that we've failed to find an object for a given id. These problems are perceived as random and are quite hard to reproduce.
+Since collection is driven by the garbage collectors it is possible to hold a weak reference to the JavaScript instance of a splice. After a V8 GC, the splice can make the reference to the Java instance weak allowing the Android VM GC to collect it. Then, if before the next V8 GC the JavaScript instance is obtained from the weak reference and its methods are called, it will result in accessing a half-dead splice (since the Java counterpart is dead already). The error reported by the runtime points out that we've failed to find an object for a given id. These problems are perceived as random and are quite hard to reproduce.
 
 #### Splices Die Fast
 Multiple splices and JavaScript instances can be created for a single Java object, properties may be lost.
diff --git a/docs/core-concepts/plugins.md b/docs/core-concepts/plugins.md
index 53c2ffa17..2a37dc5ac 100644
--- a/docs/core-concepts/plugins.md
+++ b/docs/core-concepts/plugins.md
@@ -53,7 +53,7 @@ As shown above the command **tns plugin add <plugin-name>** is actually doing **
 npm i tns-platform-declarations --save-dev
 ```
 
-> **Note:** The difference between dependencies and developer dependencies is that **dependencies** are required to run, while **devDependencies** are needed only during development. Example for dependency is the **nativescript-camera** plugin which is required runtime so you could use the hardware camera. On the other hand, the **tns-platform-declarations** is a developer dependency required only for intelliSense during the development process. The `devDependncies` should not be installed as `dependencies` to avoid large output build files (large application size). Example `package.json` file using both `dependencies` and `devDependencies` can be found [here](https://github.com/NativeScript/nativescript-sdk-examples-js/blob/master/package.json#L31-L44).
+> **Note:** The difference between dependencies and developer dependencies is that **dependencies** are required to run, while **devDependencies** are needed only during development. Example for dependency is the **nativescript-camera** plugin which is required runtime so you could use the hardware camera. On the other hand, the **tns-platform-declarations** is a developer dependency required only for intelliSense during the development process. The `devDependencies` should not be installed as `dependencies` to avoid large output build files (large application size). Example `package.json` file using both `dependencies` and `devDependencies` can be found [here](https://github.com/NativeScript/nativescript-sdk-examples-js/blob/master/package.json#L31-L44).
 
 ## Importing and Using Plugins 
 
diff --git a/docs/core-concepts/properties.md b/docs/core-concepts/properties.md
index 50319be6e..3ae5a04ae 100644
--- a/docs/core-concepts/properties.md
+++ b/docs/core-concepts/properties.md
@@ -131,7 +131,7 @@ marginBottomProperty.register(Style);
 The `CoercibleProperty` is a property that extends the base Property class by providing the capability to be coercible. For better illustration when a property might need to be coercible let's assume that we are working on `selectedIndex` property of some UI element that can hold different number of `items`. The base case would suggest that the `selectedIndex` would vary within the number of items, but what would cover the case where the items are changed dynamically (and the `selectedIndex` is not within the length range)? This is the case that can be handled by a property that can coerce the value.
 
 
-Creating the `selectedIndex` as coercible property dependend on the number of items
+Creating the `selectedIndex` as coercible property dependent on the number of items
 ```TypeScript
 export const selectedIndexProperty = new CoercibleProperty<SegmentedBarBase, number>({
     name: "selectedIndex", defaultValue: -1,
@@ -139,8 +139,8 @@ export const selectedIndexProperty = new CoercibleProperty<SegmentedBarBase, num
         target.notify(<SelectedIndexChangedEventData>{ eventName: SegmentedBarBase.selectedIndexChangedEvent, object: target, oldIndex: oldValue, newIndex: newValue });
     },
 
-    // in this case the coerse value will change depending on whether the actual number of items
-    // is more or less than the value we want to appl for selectedIndex
+    // in this case the coerce value will change depending on whether the actual number of items
+    // is more or less than the value we want to apply for selectedIndex
     coerceValue: (target, value) => {
         let items = target.items;
         if (items) {
@@ -280,7 +280,7 @@ Each UI element extends the `View` class (e.g., like `StackLayout` or `Label`) a
 > As an alternative, in Angular, we can get reference to the native elements using the `ViewChild` directive and the `nativeElement` property.
 >  ```HTML
 > <StackLayout #myNgStack id="myStackId">
->     <Label text="Using ViewChild agains getViewById" />
+>     <Label text="Using ViewChild against getViewById" />
 > </StackLayout>
 >  ```
 >  ```TypeScript
diff --git a/docs/core-concepts/utils.md b/docs/core-concepts/utils.md
index c912b12a7..0ea0fe065 100644
--- a/docs/core-concepts/utils.md
+++ b/docs/core-concepts/utils.md
@@ -64,12 +64,12 @@ utils.openUrl("https://docs.nativescript.org/core-concepts/utils")
  Escapes special regex symbols (., *, ^, $, etc.) in string in order to create a valid regex from it.
 
  ```JavaScript
-var samplestring = "All of these should be escaped: ^ $ * ";
-var newString = utilsModule.escapeRegexSymbols(samplestring);
+var sampleString = "All of these should be escaped: ^ $ * ";
+var newString = utilsModule.escapeRegexSymbols(sampleString);
 ```
 ```TypeScript
-var samplestring: string = "All of these should be escaped: ^ $ * ";
-var newString: string = utils.escapeRegexSymbols(samplestring);
+var sampleString: string = "All of these should be escaped: ^ $ * ";
+var newString: string = utils.escapeRegexSymbols(sampleString);
 ```
 
 ### convertString() function
@@ -140,13 +140,13 @@ var value = utils.layout.round(<number_value>);
 The method checks if the current thread is the main thread. It will directly call the passed function if it is, or dispatches it to the main thread otherwise.
 
 ```JavaScript
-utilsModule.executeOnMainThread(()=>{
-      //......     
+utilsModule.executeOnMainThread(() => {
+    // ...
 })
 ```
 ```TypeScript
-utilsModule.executeOnMainThread(()=>{
-      //......     
+utilsModule.executeOnMainThread(() => {
+    // ...
 })
 ```
 
@@ -155,13 +155,13 @@ utilsModule.executeOnMainThread(()=>{
 The method returns a function wrapper which executes the supplied function on the main thread. The wrapper behaves like the original function and passes all of its arguments BUT discards its return value.
 
 ```JavaScript
-utilsModule.mainThreadify(()=>{
-      //......     
+utilsModule.mainThreadify(() => {
+    // ...
 })
 ```
 ```TypeScript
-utilsModule.mainThreadify(()=>{
-      //......     
+utilsModule.mainThreadify(() => {
+    // ...
 })
 ```
 
@@ -215,8 +215,8 @@ Show keyboard for a specific element.
 function showKeyboard(args) {
     var button = args.object;
     var page = button.page;
-    var textfield = page.getViewById("textfieldid");
-    utilsModule.ad.showSoftInput(textfield.android);
+    var textField = page.getViewById("textfieldid");
+    utilsModule.ad.showSoftInput(textField.android);
 }
 exports.showKeyboard = showKeyboard;
 ```
@@ -225,11 +225,11 @@ import { Page } from "tns-core-modules/ui/page";
 import { TextField } from "tns-core-modules/ui/text-field";
 import { Button } from "tns-core-modules/ui/button"
 
-export function showKeyboard(args:EventData){
+export function showKeyboard(args: EventData) {
     var button: Button = <Button>args.object;
     var page: Page = <Page>button.page;
-    var textfield: TextField = <TextField> page.getViewById("textfieldid");
-    utils.ad.showSoftInput(textfield.android);
+    var textField: TextField = <TextField> page.getViewById("textfieldid");
+    utils.ad.showSoftInput(textField.android);
 }
 ```
 
@@ -248,7 +248,7 @@ function dismissSoftInput(args) {
 exports.dismissSoftInput = dismissSoftInput;
 ```
 ```TypeScript
-export function dismissSoftInput(args: EventData){
+export function dismissSoftInput(args: EventData) {
     utils.ad.dismissSoftInput();
 }
 ```
@@ -271,28 +271,28 @@ const stringSet = utils.ad.collections.stringArrayToStringSet(stringArr);
 Converts a string hash set into array of strings
 
 ```JavaScript
-var hashset = new java.util.HashSet();
+var hashSet = new java.util.HashSet();
 var string1 = new java.lang.String("item1");
 var string2 = new java.lang.String("item2");
 var string3 = new java.lang.String("item3");
     
-hashset.add(string1);
-hashset.add(string2);
-hashset.add(string3);
+hashSet.add(string1);
+hashSet.add(string2);
+hashSet.add(string3);
 
-var stringArray = utilsModule.ad.collections.stringSetToStringArray(hashset);
+var stringArray = utilsModule.ad.collections.stringSetToStringArray(hashSet);
 ```
 ```TypeScript
-const hashset = new java.util.HashSet();
+const hashSet = new java.util.HashSet();
 const string1 = new java.lang.String("item1");
 const string2 = new java.lang.String("item2");
 const string3 = new java.lang.String("item3");
     
-hashset.add(string1);
-hashset.add(string2);
-hashset.add(string3);
+hashSet.add(string1);
+hashSet.add(string2);
+hashSet.add(string3);
 
-var stringArray = utils.ad.collections.stringSetToStringArray(hashset);
+var stringArray = utils.ad.collections.stringSetToStringArray(hashSet);
 ```
 
 #### getDrawableId() function
@@ -303,7 +303,7 @@ Returns the drawable id from a given resource name
 var drawableId = utilsModule.ad.resources.getDrawableId("icon");
 ```
 ```TypeScript
-const drawableId:number = utils.ad.resources.getDrawableId("icon");
+const drawableId: number = utils.ad.resources.getDrawableId("icon");
 ```
 
 #### getStringId() function
@@ -349,11 +349,11 @@ Converts a JavaScript array to a [NSArray](https://developer.apple.com/library/i
 
 ```JavaScript
 var jsArray = ["item1", "item2", "item3"];
-var nsarray = utilsModule.ios.collections.jsArrayToNSArray(jsArray);
+var nsArray = utilsModule.ios.collections.jsArrayToNSArray(jsArray);
 ```
 ```TypeScript
-const jsArray:Array<string> = ["item1", "item2", "item3"];
-const nsarray = utils.ios.collections.jsArrayToNSArray(jsArray);
+const jsArray: Array<string> = ["item1", "item2", "item3"];
+const nsArray = utils.ios.collections.jsArrayToNSArray(jsArray);
 ```
 
 #### nsArrayToJSArray() function
@@ -361,12 +361,12 @@ const nsarray = utils.ios.collections.jsArrayToNSArray(jsArray);
 Converts a NSArray to a JavaScript array.
 
 ```JavaScript
-var nsarray = new NSArray(["item1", "item2", "item3"]);
-var jsarray = utilsModule.ios.collections.nsArrayToJSArray(nsarray);
+var nsArray = new NSArray(["item1", "item2", "item3"]);
+var jsArray = utilsModule.ios.collections.nsArrayToJSArray(nsArray);
 ```
 ```TypeScript
-const nsarray = new NSArray(["item1", "item2", "item3"]);
-const jsarray: Array<any> = utils.ios.collections.nsArrayToJSArray(nsarray);
+const nsArray = new NSArray(["item1", "item2", "item3"]);
+const jsArray: Array<any> = utils.ios.collections.nsArrayToJSArray(nsArray);
 ```
 
 #### isLandscape() function
diff --git a/docs/plugins/Android-Plugins-Infrastructure.md b/docs/plugins/Android-Plugins-Infrastructure.md
index 634b9af22..138c1ddf7 100644
--- a/docs/plugins/Android-Plugins-Infrastructure.md
+++ b/docs/plugins/Android-Plugins-Infrastructure.md
@@ -76,7 +76,7 @@ We are concentrating on the "_native_" part of the plugin. When we talk about "_
 
 ### What do I use?
 
-When you want to create an Android NativeScript plugin and you want to add some "_native_" functionality there are two main options. Use a `.jar` file, or use a `.aar` file. Keep in mind that `.aar` files are the recomended library form for NativeScript plugins. When we use a library in the form of a `.jar` file we want some functionality that doesn’t need any resources, just native implementation of some logic we need. For example, if we need to make some complicated calculation and there is an SDK in the form of a `.jar` file and requires **no** UI elements, we could use that library. This would only provide a couple of classes with some logic in them and **should not** declare activities or any other types of application components (http://www.tutorialspoint.com/android/android_application_components.htm).
+When you want to create an Android NativeScript plugin and you want to add some "_native_" functionality there are two main options. Use a `.jar` file, or use a `.aar` file. Keep in mind that `.aar` files are the recommended library form for NativeScript plugins. When we use a library in the form of a `.jar` file we want some functionality that doesn’t need any resources, just native implementation of some logic we need. For example, if we need to make some complicated calculation and there is an SDK in the form of a `.jar` file and requires **no** UI elements, we could use that library. This would only provide a couple of classes with some logic in them and **should not** declare activities or any other types of application components (http://www.tutorialspoint.com/android/android_application_components.htm).
 
 * In what cases should we prefer `.jar` files?
     * when we don’t have any need for using android application components
@@ -84,7 +84,7 @@ When you want to create an Android NativeScript plugin and you want to add some
     * when we don’t need resources connected to the `.jar` file like drawables, layouts, etc.
 
 * In what cases should we prefer `.aar` files:
-    * when we want to use some kind of an interactive SDK like facebook, dropbox, youtube, etc.
+    * when we want to use some kind of an interactive SDK like Facebook, Dropbox, YouTube, etc.
     * when we need to use application components like activities, services, resources, etc.
 
 > **IMPORTANT:**  The recommended way of using AAR files inside a NativeScript plugin is to add it as a dependency in the `include.gradle` file inside the `platforms/android` folder of the plugin.
diff --git a/docs/plugins/implementing-core-theme.md b/docs/plugins/implementing-core-theme.md
index 77d3c90a9..26122cf3b 100644
--- a/docs/plugins/implementing-core-theme.md
+++ b/docs/plugins/implementing-core-theme.md
@@ -50,7 +50,7 @@ Review [NativeScript Core Theme supported skins] ({ % https://github.com/NativeS
 
 ### Files Structure and Contents
 
-Add folder `scss` to your plugin soucre folder having the following structure:
+Add folder `scss` to your plugin source folder having the following structure:
 
 ```
 scss
@@ -130,7 +130,7 @@ $mybtn-background-color: $lime;
 $mybtn-color: $black;
 ```
 
-`platforms\_mybutton.android.scss` and `platforms\_mybutton.ios.scss` override some of the variables depending on the platfom - iOS or Android.
+`platforms\_mybutton.android.scss` and `platforms\_mybutton.ios.scss` override some of the variables depending on the platform - iOS or Android.
 
 platforms\_mybutton.android.scss:
 ````
diff --git a/docs/plugins/ui-plugin-custom.md b/docs/plugins/ui-plugin-custom.md
index c4d9e26a6..c1930d72f 100644
--- a/docs/plugins/ui-plugin-custom.md
+++ b/docs/plugins/ui-plugin-custom.md
@@ -216,7 +216,7 @@ export class MyButton extends MyButtonBase {
     // Alpha could be controlled from Android theme.
     // Thus we take the default native value from the nativeView.
     // If view is recycled the value returned from this method
-    // will be passed to [myOppacityProperty.setNative]
+    // will be passed to [myOpacityProperty.setNative]
     [myOpacityProperty.getDefault](): number {
         return this.nativeView.getAlpha()
     }
@@ -303,7 +303,7 @@ export class MyButton extends MyButtonBase {
 
     // gets the default native value for opacity property.
     // If view is recycled the value returned from this method
-    // will be passed to [myOppacityProperty.setNative]
+    // will be passed to [myOpacityProperty.setNative]
     [myOpacityProperty.getDefault](): number {
         return this.nativeView.alpha;
     }
diff --git a/docs/sidekick/user-guide/enterprise-auth/openid.md b/docs/sidekick/user-guide/enterprise-auth/openid.md
index 00aacdd71..0631c4e1b 100644
--- a/docs/sidekick/user-guide/enterprise-auth/openid.md
+++ b/docs/sidekick/user-guide/enterprise-auth/openid.md
@@ -50,7 +50,7 @@ There are a lot of fields by which you can configure the OpenID authentication s
 		</tr>
 		<tr>
 			<td><code>Issuer identifier</code></td>
-			<td align="center">This is a case-sensistive URL that identifies the issuer of the response.</td>
+			<td align="center">This is a case-sensitive URL that identifies the issuer of the response.</td>
 		</tr>
 		<tr>
 			<td><code>Scope</code></td>
diff --git a/docs/sidekick/user-guide/enterprise-auth/saml.md b/docs/sidekick/user-guide/enterprise-auth/saml.md
index 79d05cc8a..bce670d5b 100644
--- a/docs/sidekick/user-guide/enterprise-auth/saml.md
+++ b/docs/sidekick/user-guide/enterprise-auth/saml.md
@@ -84,7 +84,7 @@ The following steps will walk you through creating a new Azure Active Directory
 
   * For **Identifier** enter `https://auth.kinvey.com/kinvey-mobile-identity-connect`.
   * For **Reply URL** enter `https://auth.kinvey.com/v3/saml/assertion`.
-  * Click on **Show sdvanced URL settings**.
+  * Click on **Show advanced URL settings**.
   * For **Sign on URL** enter `https://auth.kinvey.com/`.
 
   ![Azure SAML settings](../../img/enterprise-auth/saml-settings-azure.png)
diff --git a/docs/tooling/angular-cli.md b/docs/tooling/angular-cli.md
index f8cde58b7..c57213d00 100644
--- a/docs/tooling/angular-cli.md
+++ b/docs/tooling/angular-cli.md
@@ -1,6 +1,6 @@
 ---
 title: Angular CLI
-description: Learn how to use the Angular CLI in your NativeScript app with @nativescript/schematics. The extension to Angular Schematisc allows you to use the Angular CLI in both NativeScript Angular projects and web+mobile code-sharing projects.
+description: Learn how to use the Angular CLI in your NativeScript app with @nativescript/schematics. The extension to Angular Schematics allows you to use the Angular CLI in both NativeScript Angular projects and web+mobile code-sharing projects.
 position: 80
 environment: angular
 ---
diff --git a/docs/tooling/debugging/chrome-devtools.md b/docs/tooling/debugging/chrome-devtools.md
index e652e5391..db6efc8a8 100644
--- a/docs/tooling/debugging/chrome-devtools.md
+++ b/docs/tooling/debugging/chrome-devtools.md
@@ -167,7 +167,7 @@ Writing plugins is a great way to give back to the community by making applicati
 -	Network requests in plugins - **Note**: __The following content concerns only plugin authors who wrap and expose **Android** (Network agent in DevTools not yet supported with a public API in the iOS runtime) http functionalities.__
     To make your http functionality debuggable, there are callbacks you need to call at certain times of the lifecycle of the network request, following a [specific protocol](https://chromedevtools.github.io/devtools-protocol/tot/Network/). For your convenience,In order to we've exposed callbacks and [TypeScript interfaces](https://github.com/NativeScript/NativeScript/blob/8f621a0df0f5c5660ed784944470e47bd6133825/tns-core-modules/debugger/debugger.ts#L48) to facilitate sending information to the Network agent.
 
-    - Immediatelly before making the request:
+    - Immediately before making the request:
 
         Check if the `global.__inspector` object is available, and whether the DevTools are connected:
         ```JavaScript
diff --git a/docs/tooling/testing/end-to-end-testing/continuous-integration.md b/docs/tooling/testing/end-to-end-testing/continuous-integration.md
index ecfcea23e..54d05c9be 100644
--- a/docs/tooling/testing/end-to-end-testing/continuous-integration.md
+++ b/docs/tooling/testing/end-to-end-testing/continuous-integration.md
@@ -17,6 +17,6 @@ Once you have a set of tests, it's good to run them on a regular basis or when a
 - [SauceLabs](https://saucelabs.com/)
 
 
-A descriptive real example of CI you can find in [Plugin UI Tests]({% slug plugin-ui-tests %}#continuous-integration) article that demostrates step by step all the needed actions.
+A descriptive real example of CI you can find in [Plugin UI Tests]({% slug plugin-ui-tests %}#continuous-integration) article that demonstrates step by step all the needed actions.
 
 In short, you need a .travis.xml on the root of the repository which tells travis what machine instances to setup and which commands to execute. Then in the UI testing stage defined in your travis file, run the nativescript-dev-appium command you usually use by providing proper *--runType* and just add *--sauceLab* flag that tells plugin to execute tests in SauceLabs instead locally.
diff --git a/docs/tooling/testing/end-to-end-testing/customization.md b/docs/tooling/testing/end-to-end-testing/customization.md
index 9e6c4b44c..e001a56ba 100644
--- a/docs/tooling/testing/end-to-end-testing/customization.md
+++ b/docs/tooling/testing/end-to-end-testing/customization.md
@@ -36,7 +36,7 @@ my-plugin
 ```
 Thus, the same configuration can be used by both apps without duplication of files.
 
-If you wish to use another location of the capapabilities file instead default ones, you can specify it with `--appiumCapsLocation` option. Remember that the path provided has to be relative to the root directory.
+If you wish to use another location of the capabilities file instead default ones, you can specify it with `--appiumCapsLocation` option. Remember that the path provided has to be relative to the root directory.
 
 Notice that once custom capabilities are provided you will be able to pick any of them using the `--runType` option (e.g. `--runType android25`). See sample content of `appium.capabilities.json` file below. For more details regarding the Appium Capabilities read [Appium documentation about Desired Capabilities](https://appium.io/docs/en/writing-running-appium/caps/):
 
diff --git a/docs/tooling/testing/end-to-end-testing/getting-started.md b/docs/tooling/testing/end-to-end-testing/getting-started.md
index d7f265d62..e87e3c427 100644
--- a/docs/tooling/testing/end-to-end-testing/getting-started.md
+++ b/docs/tooling/testing/end-to-end-testing/getting-started.md
@@ -55,7 +55,7 @@ Here is more info about the E2E test specific files and configurations:
 
 Generated tests are standard [Mocha](http://mochajs.org) tests.
 
-> Note - in case you want to execute image comparision while testing there are two more important folders to have in mind: 
+> Note - in case you want to execute image comparison while testing there are two more important folders to have in mind: 
 > * `e2e/reports` - it is created during test execution and stores the actual images from comparison
 > * `e2e/resources` - this folder aims to store the expected images for comparison
 
@@ -69,7 +69,7 @@ $ tns build ios
 ```
 
 The command that will run the tests should specify the targeted capabilities configuration using the `runType` option as shown below. This way a capabilities configuration will be selected from the [capabilities]({% slug e2e-testing-customization %}#custom-appium-capabilities) configuration file.
-> Appium capabilities are a JSON object describing how to run your test - what plarform to use, which version, where your app is located, etc. Read more about [capabilities in the official Appium documentaion](http://appium.io/docs/en/writing-running-appium/caps/).
+> Appium capabilities are a JSON object describing how to run your test - what plarform to use, which version, where your app is located, etc. Read more about [capabilities in the official Appium documentation](http://appium.io/docs/en/writing-running-appium/caps/).
 
 > To understand more about how to create custom capabilities, you can refer to the [Customization section in this documentation]({% slug e2e-testing-customization %}).
 
@@ -80,7 +80,7 @@ $ npm run e2e -- --runType <capability-name>
 
 where `<capability-name>` is defined in `<your-app-folder>/e2e/config/appium.capabilities.json`. You can choose any of the predefined ones or [create new ones](({% slug e2e-testing-customization %}#custom-appium-capabilities)) before running the tests. This will asure you that you are executing the tests against the platform and version you want to.
 
-For Android, make sure that the `deviceName` and `avd` match the name of an existing AVD. We recommend using underscrores as separators in the name i.e. `Pixel_API_28`.
+For Android, make sure that the `deviceName` and `avd` match the name of an existing AVD. We recommend using underscores as separators in the name i.e. `Pixel_API_28`.
 
 For iOS, you also need to make sure that the `deviceName` and `platformVersion` are configured in the Simulator app.