chore: fix some typos (#3891)

### Goals :soccer:
Fix some typos.

### Testing Details :mag:
Installed firewalk, started it and ran `swift test` - tests passing.

CHANGELOG.md

@@ -521,7 +521,7 @@ Released on 2020-05-16. All issues associated with this milestone can be found u
 - Thread-safety issue in `Session`.
   - Fixed by [Jon Shier](https://github.com/jshier) in Pull Request [#3179](https://github.com/Alamofire/Alamofire/pull/3179).
 - Memory leak in `NetworkReachabilityManager`.
-  - Fixed by [dirtmelon](https://github.com/dirtmelon) in Pull Reqeust [#3180](https://github.com/Alamofire/Alamofire/pull/3180).
+  - Fixed by [dirtmelon](https://github.com/dirtmelon) in Pull Request [#3180](https://github.com/Alamofire/Alamofire/pull/3180).
 
 ---
 
@@ -1943,7 +1943,7 @@ Released on 2016-05-08. All issues associated with this milestone can be found u
 - URLProtocol tests to demonstrate using `NSURLProtocol` with `NSURLSession`.
   - Updated by [Christian Noon](https://github.com/cnoon) in regards to Issue
     [#1160](https://github.com/Alamofire/Alamofire/issues/1160).
-- The `SesionDelegate` to no longer be `final` to allow subclassing.
+- The `SessionDelegate` to no longer be `final` to allow subclassing.
   - Updated by [Christian Noon](https://github.com/cnoon) in Pull Request
     [#1172](https://github.com/Alamofire/Alamofire/issues/1172) in regards to Issue
     [#1145](https://github.com/Alamofire/Alamofire/issues/1145).
@@ -3088,7 +3088,7 @@ Released on 2015-04-09.
 #### Fixed
 
 - Async tests where asserts were potentially not being run by by moving
-  `expectation.fullfill()` to end of closures.
+  `expectation.fulfill()` to end of closures.
   - Fixed by [Nate Cook](https://github.com/natecook1000) in Pull Request
     [#420](https://github.com/Alamofire/Alamofire/pull/420).
 - Small grammatical error in the ParameterEncoding section of the README.
@@ -3196,7 +3196,7 @@ Released on 2015-01-30.
 - Spec validation error with CocoaPods 0.36.0.beta-1 by disabling -b flags in `cURL`
   debug on OSX.
   - Fixed by [Mattt Thompson](https://github.com/mattt).
-- Travis-CI build issue by adding suppport for an `iOS Example` scheme.
+- Travis-CI build issue by adding support for an `iOS Example` scheme.
   - Fixed by [Yasuharu Ozaki](https://github.com/yasuoza) in Pull Request
     [#322](https://github.com/Alamofire/Alamofire/pull/322).
 

Documentation/AdvancedUsage.md

@@ -42,7 +42,7 @@
   - [Compressing Request Body Data With `DeflateRequestCompressor`](#compressing-request-body-data-with-deflaterequestcompressor)
 - [Security](#security)
   - [Evaluating Server Trusts with `ServerTrustManager` and `ServerTrustEvaluating`](#evaluating-server-trusts-with-servertrustmanager-and-servertrustevaluating)
-    - [`ServerTrustEvaluting`](#servertrustevaluting)
+    - [`ServerTrustEvaluating`](#servertrustevaluting)
     - [`ServerTrustManager`](#servertrustmanager)
       - [Subclassing `ServerTrustManager`](#subclassing-servertrustmanager)
   - [App Transport Security](#app-transport-security)

Documentation/Alamofire 5.0 Migration Guide.md

@@ -34,7 +34,7 @@ Most APIs have changed in Alamofire 5, so this list is not complete. While most
   - `.pinCertificates` is replaced by `PinnedCertificatesTrustEvaluator`.
   - `.pinPublicKeys` is replaced by `PublicKeysTrustEvaluator`.
   - `.disableEvaluation` is replaced by `DisabledTrustEvaluator`.
-  - `.customEvaluation` is replaced by either using `CompositeTrustEvalutor` to combine existing `ServerTrustEvaluating` types or by creating a new type that conforms to `ServerTrustEvaluating`.
+  - `.customEvaluation` is replaced by either using `CompositeTrustEvaluator` to combine existing `ServerTrustEvaluating` types or by creating a new type that conforms to `ServerTrustEvaluating`.
 - `DataResponse` and `DownloadResponse` are now both doubly generic to both the response type as well as the error type. By default all Alamofire APIs return a `AF` prefixed response type, which defaults the `Error` type to `AFError`.
 - Alamofire now returns `AFError` for all of its APIs, wrapping any underlying system or custom APIs in `AFError` instances.
 - `HTTPMethod` is now a `struct` and not an `enum` and can be expanded to provide custom methods.

Source/Features/AuthenticationInterceptor.swift

@@ -126,7 +126,7 @@ public protocol Authenticator: AnyObject {
     /// credential while the request was in flight. If it has already refreshed, then we don't need to trigger an
     /// additional refresh. If it hasn't refreshed, then we need to refresh.
     ///
-    /// Now that it is understood how the result of this method is used in the refresh lifecyle, let's walk through how
+    /// Now that it is understood how the result of this method is used in the refresh lifecycle, let's walk through how
     /// to implement it. You should return `true` in this method if the `URLRequest` is authenticated in a way that
     /// matches the values in the `Credential`. In the case of OAuth2, this would mean that the Bearer token in the
     /// `Authorization` header of the `URLRequest` matches the access token in the `Credential`. If it matches, then we

Tests/DataStreamTests.swift

@@ -493,7 +493,7 @@ final class DataStreamTests: BaseTestCase {
 
         var response: HTTPURLResponse?
         var complete: DataStreamRequest.Completion?
-        let didReceive = expectation(description: "stream did receieve")
+        let didReceive = expectation(description: "stream did receive")
         let didComplete = expectation(description: "stream complete")
 
         // When

docs/Protocols/Authenticator.html

@@ -875,7 +875,7 @@ server until the refresh has completed. This is where this method comes in.</p>
 credential while the request was in flight. If it has already refreshed, then we don&rsquo;t need to trigger an
 additional refresh. If it hasn&rsquo;t refreshed, then we need to refresh.</p>
 
-<p>Now that it is understood how the result of this method is used in the refresh lifecyle, let&rsquo;s walk through how
+<p>Now that it is understood how the result of this method is used in the refresh lifecycle, let&rsquo;s walk through how
 to implement it. You should return <code>true</code> in this method if the <code>URLRequest</code> is authenticated in a way that
 matches the values in the <code><a href="../Protocols/Authenticator.html#/s:9Alamofire13AuthenticatorP10CredentialQa">Credential</a></code>. In the case of OAuth2, this would mean that the Bearer token in the
 <code>Authorization</code> header of the <code>URLRequest</code> matches the access token in the <code><a href="../Protocols/Authenticator.html#/s:9Alamofire13AuthenticatorP10CredentialQa">Credential</a></code>. If it matches, then we

docs/docsets/Alamofire.docset/Contents/Resources/Documents/Protocols/Authenticator.html

@@ -875,7 +875,7 @@ server until the refresh has completed. This is where this method comes in.</p>
 credential while the request was in flight. If it has already refreshed, then we don&rsquo;t need to trigger an
 additional refresh. If it hasn&rsquo;t refreshed, then we need to refresh.</p>
 
-<p>Now that it is understood how the result of this method is used in the refresh lifecyle, let&rsquo;s walk through how
+<p>Now that it is understood how the result of this method is used in the refresh lifecycle, let&rsquo;s walk through how
 to implement it. You should return <code>true</code> in this method if the <code>URLRequest</code> is authenticated in a way that
 matches the values in the <code><a href="../Protocols/Authenticator.html#/s:9Alamofire13AuthenticatorP10CredentialQa">Credential</a></code>. In the case of OAuth2, this would mean that the Bearer token in the
 <code>Authorization</code> header of the <code>URLRequest</code> matches the access token in the <code><a href="../Protocols/Authenticator.html#/s:9Alamofire13AuthenticatorP10CredentialQa">Credential</a></code>. If it matches, then we

docs/docsets/Alamofire.docset/Contents/Resources/Documents/js/jazzy.js

@@ -22,7 +22,7 @@ function itemLinkToContent($link) {
   return $link.parent().parent().next();
 }
 
-// On doc load + hash-change, open any targetted item
+// On doc load + hash-change, open any targeted item
 function openCurrentItemIfClosed() {
   if (window.jazzy.docset) {
     return;

docs/js/jazzy.js

@@ -22,7 +22,7 @@ function itemLinkToContent($link) {
   return $link.parent().parent().next();
 }
 
-// On doc load + hash-change, open any targetted item
+// On doc load + hash-change, open any targeted item
 function openCurrentItemIfClosed() {
   if (window.jazzy.docset) {
     return;