Fix spelling errors in AlignAssignmentStatement code and docs

Co-authored-by: andyleejordan <2226434+andyleejordan@users.noreply.github.com>

Author: Copilot

Rules/AlignAssignmentStatement.cs

@@ -87,7 +87,7 @@ public override IEnumerable<DiagnosticRecord> AnalyzeScript(Ast ast, string file
 
             // As an optimisation, we first build a dictionary of all of the
             // assignment operators in the script, keyed by line number. We do
-            // this by doing a single scan of the tokens. This makes it trvially
+            // this by doing a single scan of the tokens. This makes it trivially
             // fast to find the `Equals` token for a given assignment.
 
             // Note: In instances where there is a parse error, we do not have
@@ -569,7 +569,7 @@ List<Tuple<IScriptExtent, IScriptExtent>> assignmentSites
             }
 
             // Filter out everything from assignmentSites that is not on
-            // it's own line. Do this by grouping by the start line number
+            // its own line. Do this by grouping by the start line number
             // of the lhsTokenExtent, and only keeping groups with a count
             // of 1.
             assignmentSites = assignmentSites

docs/Rules/AlignAssignmentStatement.md

@@ -155,7 +155,7 @@ enum Enum {
 #### IncludeValuelessEnumMembers: bool (Default value is `$true`)
 
 Include enum members in the alignment that don't have an initial value - that
-is to say they don't have an equals sign. Enum's don't need to be given a value
+is to say they don't have an equals sign. Enums don't need to be given a value
 when they're defined.
 
 Consider the following: