Correct some spelling mistakes (#3141)

* Correct spelling mistakes

* Correct spelling mistakes in annotations

* Correct spelling mistakes in annotations

* Revert "Correct spelling mistakes in annotations"

This reverts commit 2a510e3.

* Fix incorrect modifications

Author: Kalmaegi

Tests/Foundation/Tests/TestAttributedStringSupport.swift

@@ -59,7 +59,7 @@ extension AttributeScopes.TestAttributes {
 
     enum TestForegroundColorAttribute: CodableAttributedStringKey, MarkdownDecodableAttributedStringKey {
         typealias Value = Color
-        static let name = "ForgroundColor"
+        static let name = "ForegroundColor"
     }
 
     enum TestBackgroundColorAttribute: CodableAttributedStringKey, MarkdownDecodableAttributedStringKey {

Tests/Foundation/Tests/TestDateFormatter.swift

@@ -459,7 +459,7 @@ class TestDateFormatter: XCTestCase {
             let parsed = formatter.date(from: "令和1年5月1日 23:10")
             XCTAssertEqual(parsed?.timeIntervalSince1970, 1556719800) // May 1st, 2019, 11:10 PM (JST)
 
-            // Test for 元年(Gannen) representaion of 1st year
+            // Test for 元年(Gannen) representation of 1st year
             let parsedAlt = formatter.date(from: "令和元年5月1日 23:10")
             XCTAssertEqual(parsedAlt?.timeIntervalSince1970, 1556719800) // May 1st, 2019, 11:10 PM (JST)
 

Tests/Foundation/Tests/TestFileManager.swift

@@ -1505,7 +1505,7 @@ VIDEOS=StopgapVideos
 
         // Some of these tests will throw an NSException on Darwin which would be normally be
         // modelled by a fatalError() or other hard failure, however since most of these functions
-        // are thorwable, an NSError is thrown instead which is more useful.
+        // are throwable, an NSError is thrown instead which is more useful.
         let fm = FileManager.default
 
         XCTAssertNil(fm.homeDirectory(forUser: ""))

Tests/Foundation/Tests/TestNSData.swift

@@ -570,7 +570,7 @@ class TestNSData: LoopbackServerTest {
     }
 
 #if !os(Windows)
-    // NOTE: `umask(3)` is process global. Therefore, the behavior is unknown if `withUmask(_:_:)` is used simultaniously.
+    // NOTE: `umask(3)` is process global. Therefore, the behavior is unknown if `withUmask(_:_:)` is used simultaneously.
     private func withUmask(_ mode: mode_t, _ block: () -> Void) {
         let original = umask(mode)
         block()

Tests/Foundation/Tests/TestOperationQueue.swift

@@ -655,7 +655,7 @@ class TestOperationQueue : XCTestCase {
             op3DidRun.fulfill()
         }
 
-        // Create debendency cycle
+        // Create dependency cycle
         op1.addDependency(op2)
         op2.addDependency(op3)
         op3.addDependency(op1)

Tests/Foundation/Tests/TestURLProtectionSpace.swift

@@ -155,7 +155,7 @@ class TestURLProtectionSpace : XCTestCase {
         XCTAssertEqual(param1_1_3.name, "other")
         XCTAssertEqual(param1_1_3.value, "be2e96ad8ab8acb7ccfb49bc7e162914")
 
-        // Several chalenges, but only two of them should be valid
+        // Several challenges, but only two of them should be valid
         let challenges2 = _HTTPURLProtocol._HTTPMessage._Challenge.challenges(from: "Digest realm=\"Unsupported\", Basic, basic realm =    \"First \\\" realm\", Basic realm=\"Second realm\"")
         XCTAssertEqual(challenges2.count, 2, "String contains 2 valid challenges")
         let challenge2_1 = try XCTUnwrap(challenges2.first)