docs: fix a bunch of typos in SWBCore specs (#187)

Author: MojtabaHs

Sources/SWBCore/Specs/CommandLineToolSpec.swift

@@ -15,7 +15,7 @@ public import struct Foundation.Data
 public import class Foundation.JSONDecoder
 public import SWBMacro
 
-/// Describes the type and other characterstics of a single kind of input file accepted by a build tool.
+/// Describes the type and other characteristics of a single kind of input file accepted by a build tool.
 struct InputFileTypeDescriptor: Encodable, Sendable {
     /// Identifier of the file type — this is unbound until the build tool is used, since the particular file type any given identifier maps to can depend on the context.
     let identifier: String
@@ -509,7 +509,7 @@ open class CommandLineToolSpec : PropertyDomainSpec, SpecType, TaskTypeDescripti
             } else if let inherited = (basedOnSpec as? CommandLineToolSpec)?.outputs {
                 self.outputs = inherited
             } else {
-                // If the tool defined no outputs then force the definition of one using $(OutputPath). This correpsonds to the effective behavior of Xcode, which would implicitly create the output node when the spec asked for [output].
+                // If the tool defined no outputs then force the definition of one using $(OutputPath). This corresponds to the effective behavior of Xcode, which would implicitly create the output node when the spec asked for [output].
                 //
                 // FIXME: Force the specs to define this, instead of synthesizing it: <rdar://problem/24544779> [Swift Build] Stop synthesizing Outputs for generic command line tools
                 self.outputs = [parser.delegate.internalMacroNamespace.parseString("$(OutputPath)")]
@@ -1417,7 +1417,7 @@ open class GenericCommandLineToolSpec : CommandLineToolSpec, @unchecked Sendable
 /// A general-purpose output parser for scraping traditional POSIX-style diagnostics.  Output is passed through to the delegate as it is received, while diagnostic parsing is done line-by-line as each newline is encountered.
 open class GenericOutputParser : TaskOutputParser {
 
-    /// The delegate that's informed about ouput and diagnostics.
+    /// The delegate that's informed about output and diagnostics.
     public let delegate: any TaskOutputParserDelegate
 
     /// Workspace context associated with the output parser.
@@ -1470,7 +1470,7 @@ open class GenericOutputParser : TaskOutputParser {
         // Following that, there must be a diagnostic kind keyword or a basename
         // alias, and then a diagnostic.
         //
-        // We also retrict the leading indicator to not have any quote characters,
+        // We also restrict the leading indicator to not have any quote characters,
         // which helps filter out anything which looks like a diagnostic but is
         // appearing within a quoted string.
         self.diagnosticRegex = try! RegEx(pattern: "^([^'\"]+: +|[ \\t\\f\\p{Z}]*)(error|warning|note|notice|fixit|\(toolnameSubregex)): (.*)$")

Sources/SWBCore/Specs/CoreBuildSystem.xcspec

@@ -1757,7 +1757,7 @@ When `GENERATE_INFOPLIST_FILE` is enabled, sets the value of the [CFBundleIdenti
 * When set to Automatic, this target's immediate dependencies which build dynamic libraries or frameworks and are in its Link Binaries With Libraries will automatically be built as mergeable libraries and merged into this target's binary during release builds, or reexported during debug builds.
 * When set to Manual, only immediate dependencies which have Build Mergeable Library explicitly enabled will be merged or reexported.
 
-For more information on mergable libraries, see [Configuring your project to use mergeable libraries](https://developer.apple.com/documentation/xcode/configuring-your-project-to-use-mergeable-libraries).";
+For more information on mergeable libraries, see [Configuring your project to use mergeable libraries](https://developer.apple.com/documentation/xcode/configuring-your-project-to-use-mergeable-libraries).";
             },
             {
                 Name = "AUTOMATICALLY_MERGE_DEPENDENCIES";
@@ -1777,7 +1777,7 @@ For more information on mergable libraries, see [Configuring your project to use
                 DisplayName = "Build Mergeable Library";
                 Description = "For dynamic libraries and frameworks, links this target's binary as a mergeable library which can be merged into the product of a target which depends on it if that target is configured to do so. This target will be linked as a mergeable library in release builds so it can be merged, but will instead be linked as a normal dynamic library to be reexported in debug builds. For other binary types, this setting has no effect.
 
-For more information on mergable libraries, see [Configuring your project to use mergeable libraries](https://developer.apple.com/documentation/xcode/configuring-your-project-to-use-mergeable-libraries).";
+For more information on mergeable libraries, see [Configuring your project to use mergeable libraries](https://developer.apple.com/documentation/xcode/configuring-your-project-to-use-mergeable-libraries).";
             },
             {
                 Name = "MAKE_MERGEABLE";
@@ -1925,7 +1925,7 @@ For more information on mergable libraries, see [Configuring your project to use
         );
         DefaultValue = "compiler-default";
         DisplayName = "Text-Based InstallAPI Language Dialect";
-        Description = "Selects the langauge dialect when building `Text-Based InstallAPI`.";
+        Description = "Selects the language dialect when building `Text-Based InstallAPI`.";
         ConditionFlavors = (
           arch,
           sdk,

Sources/SWBCore/Specs/ProductTypes.swift

@@ -661,7 +661,7 @@ public final class XCTestBundleProductTypeSpec : BundleProductTypeSpec, @uncheck
         table.push(BuiltinMacros.XCTRUNNER_PRODUCT_NAME, table.namespace.parseString("$(PRODUCT_NAME)-Runner.app"))
 
         // Define TARGET_BUILD_SUBPATH so the target builds to $(TARGET_BUILD_DIR)/$(TARGET_BUILD_SUBPATH) (or slightly different for deployment location builds).
-        // <rdar://problem/18902931> Should PBXXCTestBundleProductType override BUILT_PRODUCTS_DIR when it overrides TARGET_BULD_DIR?
+        // <rdar://problem/18902931> Should PBXXCTestBundleProductType override BUILT_PRODUCTS_DIR when it overrides TARGET_BUILD_DIR?
         table.push(BuiltinMacros.TARGET_BUILD_SUBPATH, table.namespace.parseString("/$(XCTRUNNER_PRODUCT_NAME)$(_WRAPPER_CONTENTS_DIR)/PlugIns"))
         table.push(BuiltinMacros.DWARF_DSYM_FOLDER_PATH, table.namespace.parseString("$(TARGET_BUILD_DIR)"))        // Do we really want dSYMs to go inside of the host app's PlugIns dir?
 
@@ -706,7 +706,7 @@ public final class XCTestBundleProductTypeSpec : BundleProductTypeSpec, @uncheck
         }
 
         // Define TARGET_BUILD_SUBPATH so the target builds to $(TARGET_BUILD_DIR)/$(TARGET_BUILD_SUBPATH) (or slightly different for deployment location builds).
-        // <rdar://problem/18902931> Should PBXXCTestBundleProductType override BUILT_PRODUCTS_DIR when it overrides TARGET_BULD_DIR?
+        // <rdar://problem/18902931> Should PBXXCTestBundleProductType override BUILT_PRODUCTS_DIR when it overrides TARGET_BUILD_DIR?
         table.push(BuiltinMacros.TARGET_BUILD_SUBPATH, table.namespace.parseLiteralString("/\(targetBuildSubpath)"))
         table.push(BuiltinMacros.DWARF_DSYM_FOLDER_PATH, table.namespace.parseString("$(TARGET_BUILD_DIR)"))
 

Sources/SWBCore/Specs/PropertyDomainSpec.swift

@@ -223,7 +223,7 @@ private let buildOptionTypes: [String: any BuildOptionType] = [
         /// Expand to the literal dynamic value, unmodified.
         case literal
 
-        /// Expand into the given arguments, after macro expression evaluation (as appropiate for the macro type). The special macro '$(value)' can be used to refer to the dynamic value of the option.
+        /// Expand into the given arguments, after macro expression evaluation (as appropriate for the macro type). The special macro '$(value)' can be used to refer to the dynamic value of the option.
         case args(MacroStringListExpression)
 
         /// Expand to the given flag.

Sources/SWBCore/Specs/SpecRegistry.swift

@@ -44,7 +44,7 @@ public protocol SpecType: AnyObject {
     /// The name of the spec subregistry to associate with this type.
     static var subregistryName: String { get }
 
-    /// The default class type to instantiate as, if not overriden.
+    /// The default class type to instantiate as, if not overridden.
     ///
     /// By default, this will be the SpecType itself, however this can be used to force specs which do not override 'Class' to be instantiated as a separate type (which would generally be a subclass of the actual SpecType). This is useful when specs without a custom 'Class' support a different set of keys than those that do.
     static var defaultClassType: (any SpecType.Type)? { get }
@@ -657,7 +657,7 @@ public final class SpecRegistry {
 
         // Load the localized strings, if available.
         //
-        // We currently hard code a local search, asuming the xcspec file is adjacent to the `strings` file or the containing `lproj`.
+        // We currently hard code a local search, assuming the xcspec file is adjacent to the `strings` file or the containing `lproj`.
         func loadLocalizedStrings(_ path: Path) -> [String: String]? {
             if let data = try? PropertyList.fromPath(path, fs: localFS) {
                 // If we found a property list, it should be a map of strings.
@@ -909,7 +909,7 @@ public final class SpecRegistry {
             print(error)
         }
 
-        // Find places where a proxy illegally depends on a spec overriden in a subdomain.
+        // Find places where a proxy illegally depends on a spec overridden in a subdomain.
         //
         // Essentially, if spec in a generic domain (foo:default) is based on an unspecified specification (bar), which is in a more specific domain 'device', then the semantics we want are that a search for 'foo:device' will return 'foo:device basedOn bar:device'. These are unfortunate semantics to implement dynamically (we want each proxy to resolve to one spec), so instead we clone any proxies that might need to satisfy this.
 

Sources/SWBCore/Specs/Specs.swift

@@ -55,7 +55,7 @@ open class Spec: @unchecked Sendable {
         return result
     }
 
-    /// The spec proxy informaton.
+    /// The spec proxy information.
     @_spi(Testing) public let proxyPath: Path
     @_spi(Testing) public let proxyDomain: String
     @_spi(Testing) public let proxyIdentifier: String