chore: fix typos (#40)

garanews · rigor789 · web-flow · commit e6de6646589e · 2021-10-08T14:58:17.000+02:00
Co-authored-by: Igor Randjelovic &lt;rigor789@gmail.com&gt;
diff --git a/advanced-concepts.md b/advanced-concepts.md
@@ -6,7 +6,7 @@ title: Advanced Concepts
 
 ## The Layout process
 
-Getting views to render with the right dimensions and positions requires a run of the layout process. When rendering, a recursive process runs through every view in the **view hiearchy** in two passes &mdash; a measure pass and a layout pass.
+Getting views to render with the right dimensions and positions requires a run of the layout process. When rendering, a recursive process runs through every view in the **view hierarchy** in two passes &mdash; a measure pass and a layout pass.
 
 During **the measure pass** every view is measured to obtain its desired size. The following properties are considered during the measuring:
 
@@ -23,7 +23,7 @@ During **the layout pass** every view is placed in a specific layout slot. The s
 The layout process is by nature an resource-intensive process and it's performance highly depends on the number views (and complexity).
 
 :::tip
-Try to keep the view hierachy as flat as possible by utilizing different [Layout Containers](/ui-and-styling#layout-containers) rather than relying on excessive view nesting.
+Try to keep the view hierarchy as flat as possible by utilizing different [Layout Containers](/ui-and-styling#layout-containers) rather than relying on excessive view nesting.
 
 **For example:** don't treat `<StackLayout>` as a `<div>` &mdash; instead try to use a `<GridLayout>` with specific `rows` and `columns` to achieve the same result:
 
@@ -42,7 +42,7 @@ Try to keep the view hierachy as flat as possible by utilizing different [Layout
 <!--  -->
 
 ```html
-<GridLayout rows="auto, auto" colums="auto, auto">
+<GridLayout rows="auto, auto" columns="auto, auto">
   <SomeItem row="0" col="0" />
   <SomeItem row="0" col="1" />
   <!-- ... row="1" ... -->
@@ -152,7 +152,7 @@ The source code of `application.android.ts` is bundled separately as `applicatio
 The `bundle.js` and `vendor.js` files are not loaded early enough in the application launch. That's why the logic in `application.android.ts` is needed to be bundled separately in order to be loaded as early as needed in the application lifecycle.
 
 ::: warning Note
-This approach will not work if aplication.android.ts requires external modules.
+This approach will not work if application.android.ts requires external modules.
 :::
 
 ### Extending Android Activity
@@ -658,7 +658,7 @@ iOS contains both an Objective-C standard library (the Foundation framework) and
 
 #### Toll-free Bridging
 
-Core Foundation has the concept of [Toll-free bridged types](https://developer.apple.com/library/ios/documentation/CoreFoundation/Conceptual/CFDesignConcepts/Articles/tollFreeBridgedTypes.html) - data types which can be used interchangably with their Objective-C counterparts. When dealing with a toll-free bridged type NativeScript always treats it as its Objective-C counterpart. Core Foundation objects on the [toll-free bridged types list](https://developer.apple.com/library/ios/documentation/CoreFoundation/Conceptual/CFDesignConcepts/Articles/tollFreeBridgedTypes.html#//apple_ref/doc/uid/TP40010677-SW4) are exposed as if they were instances of the equivalent Objective-C class. This means that a `CFDictionaryRef` value in JavaScript has the same methods on its prototype as if it were a `NSDictionary` object. Unlike regular Core Foundation objects, toll-free bridged types are automatically memory managed by NativeScript, so there is no need to retain or release them using `CFRetain` and `CFRelease`.
+Core Foundation has the concept of [Toll-free bridged types](https://developer.apple.com/library/ios/documentation/CoreFoundation/Conceptual/CFDesignConcepts/Articles/tollFreeBridgedTypes.html) - data types which can be used interchangeably with their Objective-C counterparts. When dealing with a toll-free bridged type NativeScript always treats it as its Objective-C counterpart. Core Foundation objects on the [toll-free bridged types list](https://developer.apple.com/library/ios/documentation/CoreFoundation/Conceptual/CFDesignConcepts/Articles/tollFreeBridgedTypes.html#//apple_ref/doc/uid/TP40010677-SW4) are exposed as if they were instances of the equivalent Objective-C class. This means that a `CFDictionaryRef` value in JavaScript has the same methods on its prototype as if it were a `NSDictionary` object. Unlike regular Core Foundation objects, toll-free bridged types are automatically memory managed by NativeScript, so there is no need to retain or release them using `CFRetain` and `CFRelease`.
 
 #### Null Values
 
@@ -2357,7 +2357,7 @@ After analyzing the filtering rules for a platform, {N} CLI builds final whiteli
 - If it is `true`, the final whitelist is a concatenation of all plugins' usage lists with the app's whitelist
 - Otherwise, it is equal to the app's whitelist
 
-These two lists unambigously determine how filtering is performed:
+These two lists unambiguously determine how filtering is performed:
 
 1. If the whitelist is empty, then everything is considered whitelisted by default
 2. If it contains at least one rule, only entities matching a rule are considered whitelisted
diff --git a/best-practices/android-tips.md b/best-practices/android-tips.md
@@ -10,7 +10,7 @@ On Android images inside the various drawable directories are used to serve the
 
 Google provides a great resource to learn more about [supporting different pixel densities](https://developer.android.com/training/multiscreen/screendensities).
 
-In our NativeScript project, you will have the `App_Resources/Android` directory. Everything in here will mirror a standard Android project. Inside the `App_Resources/Android/src/main` directory you shuld have a `res` directory which contains many `drawable-...` directories. This is where you should place images that have been resized for the different device displays. To read more on this topic you can read [the Android documentation for alternative bitmaps](https://developer.android.com/training/multiscreen/screendensities#TaskProvideAltBmp).
+In our NativeScript project, you will have the `App_Resources/Android` directory. Everything in here will mirror a standard Android project. Inside the `App_Resources/Android/src/main` directory you should have a `res` directory which contains many `drawable-...` directories. This is where you should place images that have been resized for the different device displays. To read more on this topic you can read [the Android documentation for alternative bitmaps](https://developer.android.com/training/multiscreen/screendensities#TaskProvideAltBmp).
 
 There are many approaches to resizing your images for the different drawable folders. You could use Android Studio or other third party tools. For this example we will look at a tool specifically built to help NativeScript developers resize their images, [images.nativescript.rocks](https://images.nativescript.rocks/).
 
diff --git a/best-practices/index.md b/best-practices/index.md
@@ -9,7 +9,7 @@ title: Best Practices
 Over the years several distinct best practices have emerged when working with NativeScript and we'd like to outline a few here for you in hopes that you can enjoy NativeScripting as much as we do. More importantly though, that your end product gives you all the right _feels_ you expect.
 
 We are providing a sample "vanilla" NativeScript app which shows some of the bad vs. good practices for you to run and see for yourself.
-Using vanilla NativeScript is a great way to see the raw examples of why these are bad and good practices which are applicable to any frontend framework integration. Each framework integration effectively utilitizes these same practices for it's own various cases.
+Using vanilla NativeScript is a great way to see the raw examples of why these are bad and good practices which are applicable to any frontend framework integration. Each framework integration effectively utilizes these same practices for it's own various cases.
 
 Clone and see for yourself: https://github.com/NativeScript/examples-best-practices
 
diff --git a/best-practices/listviews.md b/best-practices/listviews.md
@@ -4,7 +4,7 @@ title: Best Practices with ListViews, RadListView, etc.
 
 Quite possibly the _most_ important controls available on all mobile devices which have the most impact on perceived app performance.
 
-ListView, RadListView and really any view component that utilizes some form of row recyclying with view templates/components.
+ListView, RadListView and really any view component that utilizes some form of row recycling with view templates/components.
 
 ## Bad setup
 
diff --git a/code-sharing/index.md b/code-sharing/index.md
@@ -20,13 +20,13 @@ Over the years, several lessons have emerged around scalability with JavaScript
 
 4. A good code sharing approach should clearly identify deployment/distribution lines as well as distinct platform separation allowing various shared code segments to have clear designated deployment targets allowing teams to control their own sophisticated build pipelines as they desire. Further the shared code should live within a thoughtful organizational structure that supports the ability to scale and adapt to future needs aside from the deployment targets that use the shared code.
 
-5. Within the specific scope of NativeScript's viewpoint, JavaScript is the universal langugage which provides the opportunity to share code effectively and responsibly. An approach that is based fundamentally on the strengths of JavaScript (and inherently TypeScript) is a good code sharing approach.
+5. Within the specific scope of NativeScript's viewpoint, JavaScript is the universal language which provides the opportunity to share code effectively and responsibly. An approach that is based fundamentally on the strengths of JavaScript (and inherently TypeScript) is a good code sharing approach.
 
 Notes:
 
 Framework's are often "domain specific in nature". Programming languages are often the opposite or at least more broadly applicable to a wider set of domain problems. A good code sharing approach centers itself around the programming language and not the framework.
 
-If a "code sharing solution" is maintained by a framework that can often mean there are inherent biases that interlock it's "sharable nature" with the framework, even if not intentional, it is somewhat inevitable. This breaks the first rule of a good code sharing approach.
+If a "code sharing solution" is maintained by a framework that can often mean there are inherent biases that interlock it's "shareable nature" with the framework, even if not intentional, it is somewhat inevitable. This breaks the first rule of a good code sharing approach.
 
 ## Recommendations and Solutions
 
diff --git a/interaction.md b/interaction.md
@@ -701,7 +701,7 @@ NativeScript lets you animate the following properties:
 
 :::tip Note
 
-To use `translate` or `scale` you must preceed with an object declaring both x and y values, for example `translate: { x: 100, y: 250 }` or `scale: { x: 1.5, y: 0 }`.
+To use `translate` or `scale` you must proceed with an object declaring both x and y values, for example `translate: { x: 100, y: 250 }` or `scale: { x: 1.5, y: 0 }`.
 
 :::
 
@@ -1524,7 +1524,7 @@ export function showActionDialog() {
 }
 ```
 
-#### Action Dialog Propeties
+#### Action Dialog Properties
 
 | Name               | Type            | Description                                                                                    |
 | ------------------ | --------------- | ---------------------------------------------------------------------------------------------- |
diff --git a/native-api-access.md b/native-api-access.md
@@ -51,7 +51,7 @@ Now for a short walk through of one way to go about translating Java to JavaScri
 
 3. The `getSystemService(java.lang.String)` method accepts a String. When programming in Android you can use `BATTERY_SERVICE` if the `import android.content.Context` is declared in the .java file. The compiler will know that `BATTERY_SERVICE` is the [static final string declared here](https://developer.android.com/reference/android/content/Context#BATTERY_SERVICE).
 
-   You could also write the `getSystemService("batterymanager")` using the statics constant value: "batterymanager". In your NativeScript code, you could do the same, but if you prefer to use the full namespace path to the static value, you can write it like the example does with `android.content.Context.BATTERY_SERVICE`.
+   You could also write the `getSystemService("batterymanager")` using the static constant value: "batterymanager". In your NativeScript code, you could do the same, but if you prefer to use the full namespace path to the static value, you can write it like the example does with `android.content.Context.BATTERY_SERVICE`.
 
 4. Now we have an instance of the [Android BatteryManager](https://developer.android.com/reference/android/os/BatteryManager) which is what the [docs state as the return value](https://developer.android.com/reference/android/content/Context#BATTERY_SERVICE) for this system service.
 
diff --git a/plugins/background-http.md b/plugins/background-http.md
@@ -15,7 +15,7 @@ The below attached code snippets demonstrate how to use `@nativescript/backgroun
 
 ### Uploading files
 
-Sample code for configuring the upload session. Each session must have a unique `id`, but it can have multiple tasks running simultaneously. The `id` is passed as a parameter when creating the session (the `image-upload` string in the code bellow):
+Sample code for configuring the upload session. Each session must have a unique `id`, but it can have multiple tasks running simultaneously. The `id` is passed as a parameter when creating the session (the `image-upload` string in the code below):
 
 ```javascript
 // file path and url
diff --git a/plugins/datetimepicker.md b/plugins/datetimepicker.md
@@ -133,7 +133,7 @@ The `DateTimePickerFields` has a `date` property which can be used to get its cu
 
 - Orientation
 
-The `DateTimePickerFields` have an `orientation` property which allows changing the way the fields are laid out. If the orientation is `horizontal` (the default), the fields are on the same row, if the orienation is `vertical`, the fields will be on separate rows. Here's an example in the [demo](https://github.com/NativeScript/nativescript-datetimepicker/blob/master/demo/app/home/home-page.xml#L160), [demo-angular](https://github.com/NativeScript/nativescript-datetimepicker/blob/master/demo-angular/src/app/home/home.component.html#L155) and [demo-vue](https://github.com/NativeScript/nativescript-datetimepicker/blob/master/demo-vue/app/components/Home.vue#L157) applications.
+The `DateTimePickerFields` have an `orientation` property which allows changing the way the fields are laid out. If the orientation is `horizontal` (the default), the fields are on the same row, if the orientation is `vertical`, the fields will be on separate rows. Here's an example in the [demo](https://github.com/NativeScript/nativescript-datetimepicker/blob/master/demo/app/home/home-page.xml#L160), [demo-angular](https://github.com/NativeScript/nativescript-datetimepicker/blob/master/demo-angular/src/app/home/home.component.html#L155) and [demo-vue](https://github.com/NativeScript/nativescript-datetimepicker/blob/master/demo-vue/app/components/Home.vue#L157) applications.
 
 - Auto Pick Time
 
diff --git a/plugins/detox.md b/plugins/detox.md
@@ -76,7 +76,7 @@ There should also be a file called `.detoxrc.json` in your project root.
 
 ### Configure Detox
 
-Detox must be configued to know the location of the iOS and Android app binary as well as what emulator/simulator to use.
+Detox must be configured to know the location of the iOS and Android app binary as well as what emulator/simulator to use.
 
 Open `.detoxrc.json` and make the following modifications under `configurations` for iOS and Android.
 
@@ -177,7 +177,7 @@ detox build -c ios|android
 
 ### Testing
 
-Run your tests with the folling command:
+Run your tests with the following command:
 
 ```bash
 detox test -c ios|android
diff --git a/plugins/imagepicker.md b/plugins/imagepicker.md
@@ -43,7 +43,7 @@ var imagepicker = require("@nativescript/imagepicker");
 
 ### Create imagepicker
 
-Create imagepicker in `single` or `multiple` mode to specifiy if the imagepicker will be used for single or multiple selection of images
+Create imagepicker in `single` or `multiple` mode to specify if the imagepicker will be used for single or multiple selection of images
 
 _TypeScript_
 
@@ -107,7 +107,7 @@ context
 | Option                      | Platform | Default   | Description                                                                                                                                        |
 | --------------------------- | -------- | --------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
 | mode                        | both     | multiple  | The mode if the imagepicker. Possible values are `single` for single selection and `multiple` for multiple selection.                              |
-| minimumNumberOfSelection    | iOS      | 0         | The minumum number of selected assets.                                                                                                             |
+| minimumNumberOfSelection    | iOS      | 0         | The minimum number of selected assets.                                                                                                             |
 | maximumNumberOfSelection    | iOS      | 0         | The maximum number of selected assets.                                                                                                             |
 | showsNumberOfSelectedAssets | iOS      | True      | Display the number of selected assets.                                                                                                             |
 | prompt                      | iOS      | undefined | Display prompt text when selecting assets.                                                                                                         |
diff --git a/plugins/local-notifications.md b/plugins/local-notifications.md
@@ -63,7 +63,7 @@ There is a [Vue demo](https://github.com/EddyVerbruggen/nativescript-local-notif
 ### schedule
 
 On iOS you need to ask permission to schedule a notification.
-You can have the `schedule` funtion do that for you automatically (the notification will be scheduled in case the user granted permission), or you can manually invoke `requestPermission` if that's your thing.
+You can have the `schedule` function do that for you automatically (the notification will be scheduled in case the user granted permission), or you can manually invoke `requestPermission` if that's your thing.
 
 You can pass several options to this function, everything is optional:
 
diff --git a/plugins/localize.md b/plugins/localize.md
@@ -9,7 +9,7 @@ This is a plugin for NativeScript that implements internationalization (i18n) us
 
 ## Credits
 
-A lot of thanks goes out to [Ludovic Fabrèges (@lfabreges)](https://github.com/lfabreges) for developing and maintaining this plugin in the past. When he had to abandon it due to shifted priorities, he was kind enough to [move the repo to me](https://github.com/EddyVerbruggen/nativescript-localize/issues/73). Eddy then joined NativeScript's Technical Steering Committe and to vastly improve plugin maintenance [it was scoped and moved here](https://github.com/EddyVerbruggen/nativescript-localize/issues/99)!
+A lot of thanks goes out to [Ludovic Fabrèges (@lfabreges)](https://github.com/lfabreges) for developing and maintaining this plugin in the past. When he had to abandon it due to shifted priorities, he was kind enough to [move the repo to me](https://github.com/EddyVerbruggen/nativescript-localize/issues/73). Eddy then joined NativeScript's Technical Steering Committee and to vastly improve plugin maintenance [it was scoped and moved here](https://github.com/EddyVerbruggen/nativescript-localize/issues/99)!
 
 ## Table of contents
 
@@ -45,7 +45,7 @@ src
       | es.js
 ```
 
-You need to [set the default langage](#how-to-set-the-default-language) and make sure it contains
+You need to [set the default language](#how-to-set-the-default-language) and make sure it contains
 the [application name](#how-to-localize-the-application-name) to avoid any error.
 
 ### Angular
@@ -205,7 +205,7 @@ import { overrideLocale } from '@nativescript/localize'
 const localeOverriddenSuccessfully = overrideLocale('en-GB') // or "nl-NL", etc (or even just the part before the hyphen)
 ```
 
-## On Android you can programatically override this language since plugin version 4.2.1 by doing this:
+## On Android you can programmatically override this language since plugin version 4.2.1 by doing this:
 
 In your app.ts / main.ts / app.js
 
diff --git a/plugins/social-share.md b/plugins/social-share.md
diff --git a/public/api-reference/assets/js/src/lib/backbone/backbone.d.ts b/public/api-reference/assets/js/src/lib/backbone/backbone.d.ts
diff --git a/releasing.md b/releasing.md
diff --git a/security.md b/security.md
diff --git a/ui-and-styling.md b/ui-and-styling.md
