Spelling siloptimizer

* access
* accessed
* accesses
* accessor
* acquiring
* across
* activated
* additive
* address
* addresses'
* aggregated
* analysis
* and
* appropriately
* archetype
* argument
* associated
* availability
* barriers
* because
* been
* beginning
* belongs
* beneficial
* blocks
* borrow
* builtin
* cannot
* canonical
* canonicalize
* clazz
* cleanup
* coalesceable
* coalesced
* comparisons
* completely
* component
* computed
* concrete
* conjunction
* conservatively
* constituent
* construct
* consuming
* containing
* covered
* creates
* critical
* dataflow
* declaration
* defined
* defining
* definition
* deinitialization
* deliberately
* dependencies
* dependent
* deserialized
* destroy
* deterministic
* deterministically
* devirtualizes
* diagnostic
* diagnostics
* differentiation
* disable
* discipline
* dominate
* dominates
* don't
* element
* eliminate
* eliminating
* elimination
* embedded
* encounter
* epilogue
* epsilon
* escape
* escaping
* essential
* evaluating
* evaluation
* evaluator
* executing
* existential
* existentials
* explicit
* expression
* extended
* extension
* extract
* for
* from
* function
* generic
* guarantee
* guaranteed
* happened
* heuristic
* however
* identifiable
* immediately
* implementation
* improper
* include
* infinite
* initialize
* initialized
* initializer
* inside
* instruction
* interference
* interferes
* interleaved
* internal
* intersection
* intractable
* intrinsic
* invalidates
* irreducible
* irrelevant
* language
* lifetime
* literal
* looks
* materialize
* meaning
* mergeable
* might
* mimics
* modification
* modifies
* multiple
* mutating
* necessarily
* necessary
* needsmultiplecopies
* nonetheless
* nothing
* occurred
* occurs
* optimization
* optimizing
* original
* outside
* overflow
* overlapping
* overridden
* owned
* ownership
* parallel
* parameter
* paths
* patterns
* pipeline
* plottable
* possible
* potentially
* practically
* preamble
* precede
* preceding
* predecessor
* preferable
* preparation
* probably
* projection
* properties
* property
* protocol
* reabstraction
* reachable
* recognized
* recursive
* recursively
* redundant
* reentrancy
* referenced
* registry
* reinitialization
* reload
* represent
* requires
* response
* responsible
* retrieving
* returned
* returning
* returns
* rewriting
* rewritten
* sample
* scenarios
* scope
* should
* sideeffects
* similar
* simplify
* simplifycfg
* somewhat
* spaghetti
* specialization
* specializations
* specialized
* specially
* statistically
* substitute
* substitution
* succeeds
* successful
* successfully
* successor
* superfluous
* surprisingly
* suspension
* swift
* targeted
* that
* that our
* the
* therefore
* this
* those
* threshold
* through
* transform
* transformation
* truncated
* ultimate
* unchecked
* uninitialized
* unlikely
* unmanaged
* unoptimized key
* updataflow
* usefulness
* utilities
* villain
* whenever
* writes

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

lib/SILOptimizer/Mandatory/DefiniteInitialization.cpp

@@ -807,7 +807,7 @@ void LifetimeChecker::diagnoseBadExplicitStore(SILInstruction *Inst) {
   diagnose(Module, Inst->getLoc(), diag::explicit_store_of_compilerinitialized);
 }
 
-/// Determines whether the given function is a constructor that belogs to a
+/// Determines whether the given function is a constructor that belongs to a
 /// distributed actor declaration.
 /// \returns nullptr if false, and the class decl for the actor otherwise.
 static ClassDecl* getDistributedActorOfCtor(SILFunction &F) {
@@ -1653,7 +1653,7 @@ static bool isFailableInitReturnUseOfEnum(EnumInst *EI) {
 /// Given a load instruction, return true iff the result of the load is used
 /// in a return instruction directly or is lifted to an optional (i.e., wrapped
 /// into .some) and returned. These conditions are used to detect whether the
-/// given load instruction is autogenerated for a return from the initalizers:
+/// given load instruction is autogenerated for a return from the initializers:
 /// `init` or `init?`, respectively. In such cases, the load should not be
 /// considered as a use of the value but rather as a part of the return
 /// instruction. We emit a specific diagnostic in this case.
@@ -3060,7 +3060,7 @@ handleConditionalDestroys(SILValue ControlVariableAddr) {
       assert(!Availability.isAllYes() &&
              "Should not end up here if fully initialized");
 
-      // For root class initializers, we check if all proeprties were
+      // For root class initializers, we check if all properties were
       // dynamically initialized, and if so, treat this as a release of
       // an initialized 'self', instead of tearing down the fields
       // one by one and deallocating memory.