[docs] typofixes (#18920)

docs/guide/helper-json.md

@@ -4,7 +4,7 @@ Json Helper
 Json helper provides a set of static methods for encoding and decoding JSON.
 It handles encoding errors and the `[[yii\helpers\Json::encode()]]` method will not encode a JavaScript expression that is represented in 
 terms of a `[[yii\web\JsExpression]]` object.
-By default, ecoding is done with the `JSON_UNESCAPED_SLASHES | JSON_UNESCAPED_UNICODE` options.
+By default, encoding is done with the `JSON_UNESCAPED_SLASHES | JSON_UNESCAPED_UNICODE` options.
 Please see [PHP:json_encode](https://secure.php.net/manual/en/function.json-encode.php) for more information.
 
 ## Pretty Print <span id="pretty-print"></span>

docs/guide/rest-quick-start.md

@@ -190,7 +190,7 @@ For example, the URL `http://localhost/users?fields=id,email` will only return t
 > such as `password_hash`, `auth_key`. You certainly do not want these to appear in your API result.
 > You can and should remove these fields from result as described in the [Resources](rest-resources.md) section.
 
-Addionally, you can sort collections like `http://localhost/users?sort=email` or
+Additionally, you can sort collections like `http://localhost/users?sort=email` or
 `http://localhost/users?sort=-email`. Filtering collections like `http://localhost/users?filter[id]=10` or
 `http://localhost/users?filter[email][like]=gmail.com` could be implemented using
 data filters. See [Resources](rest-resources.md#filtering-collections) section for details.

docs/guide/security-authorization.md

@@ -281,7 +281,7 @@ build the hierarchy itself won't be different.
 You can use [migrations](db-migrations.md)
 to initialize and modify hierarchy via APIs offered by `authManager`.
 
-Create new migration using `./yii migrate/create init_rbac` then impement creating a hierarchy:
+Create new migration using `./yii migrate/create init_rbac` then implement creating a hierarchy:
 
 ```php
 <?php

docs/guide/tutorial-performance-tuning.md

@@ -190,7 +190,7 @@ composer dumpautoload -o
 Additionally you may consider using
 [authoritative class maps](https://getcomposer.org/doc/articles/autoloader-optimization.md#optimization-level-2-a-authoritative-class-maps)
 and [APCu cache](https://getcomposer.org/doc/articles/autoloader-optimization.md#optimization-level-2-b-apcu-cache).
-Note that both opmizations may or may not be suitable for your particular case.
+Note that both optimizations may or may not be suitable for your particular case.
 
 
 ## Processing Data Offline <span id="processing-data-offline"></span>
@@ -222,4 +222,4 @@ The following profiling tools may be useful:
 
 ## Prepare application for scaling
 
-When nothing helps you may try making your application scalabe. A good introduction is provided in [Configuring a Yii 2 Application for an Autoscaling Stack](https://github.com/samdark/yii2-cookbook/blob/master/book/scaling.md).
+When nothing helps you may try making your application scalable. A good introduction is provided in [Configuring a Yii 2 Application for an Autoscaling Stack](https://github.com/samdark/yii2-cookbook/blob/master/book/scaling.md).

docs/internals/core-code-style.md

@@ -152,7 +152,7 @@ class Foo
  * Checks whether the IP is in subnet range
  *
  * @param string $ip an IPv4 or IPv6 address
- * @param int $cidr the CIDR lendth
+ * @param int $cidr the CIDR length
  * @param string $range subnet in CIDR format e.g. `10.0.0.0/8` or `2001:af::/64`
  * @return bool whether the IP is in subnet range
  */

docs/internals/release.md

@@ -77,7 +77,7 @@ before.
 - create a new branch `2.0` from `master`
 - ensure composer.json does not contain a branch alias on this branch anymore.
 - merge necessary changes from `master` to `2.1`
-- point `master` to the lastest commit on `2.1`
+- point `master` to the latest commit on `2.1`
 - adjust composer.json branch alias for master to `2.1.x-dev`.
 - delete `2.1` branch