Merge pull request #1933 from gibachan/fix-typos

Fix typos in some .md files

Author: ahoppen

CodeGeneration/README.md

@@ -5,7 +5,7 @@ This directory contains file to generate source code that is part of the SwiftSy
 Some source code inside SwiftSyntax is generated using [SwiftSyntaxBuilder](../Sources/SwiftSyntaxBuilder), a Swift library whose purpose is to generate Swift code using Swift itself. This kind of code generation is performed by the Swift package defined in this directory.
 
 This directory is a standalone package that uses swift-syntax from the outer directory. 
-If you are making significant changs to `CodeGeneration` locally and want to avoid breaking the build of `CodeGeneration` itself by generating new files in the parent swift-syntax package, it is encouraged to change the dependency from
+If you are making significant changes to `CodeGeneration` locally and want to avoid breaking the build of `CodeGeneration` itself by generating new files in the parent swift-syntax package, it is encouraged to change the dependency from
 ```swift
 .package(path: "..")
 ```

EditorExtension/README.md

@@ -64,7 +64,7 @@ sub-menu, so mousing over it will reveal all of the actions that the editor
 extension detected at start up.
 
 Selecting a refactoring action will run it over the entire file. The plugin
-executes the corresponding `RefactoringProvider` and, whenever it recieves a
+executes the corresponding `RefactoringProvider` and, whenever it receives a
 non-`nil` response, it performs a structured edit of the syntax of the code.
 
 ## Troubleshooting

Sources/SwiftParser/SwiftParser.docc/FixingBugs.md

@@ -65,13 +65,13 @@ To add a new, more contextual diagnostic, perform the following steps.
     ```
 2. Mark the location at which you expect the diagnostic to be produced with `1️⃣`. If you expect multiple diagnostics to be produced, you can use multiple of these markers with different names and use these markers by passing a `locationMarker` to `DiagnosticSpec`. The list of valid marker emojis can be found in `Character.isMarkerEmoji`.
 3. Determine which node encompasses all information that is necessary to produce the improved diagnostic – for example `FunctionSignatureSyntax` contains all information to diagnose if the `throws` keyword was written after the `->` instead of in front of it.
-4. If the diagnostic message you want to emit does not exist yet, add a case to `StaticParserError` for the new diagnostic. If the diagnostic needs to take parameters, add a new struct to in `ParserDiagnsoticMessages.swift`.
+4. If the diagnostic message you want to emit does not exist yet, add a case to `StaticParserError` for the new diagnostic. If the diagnostic needs to take parameters, add a new struct to in `ParserDiagnosticMessages.swift`.
 5. If the function does not already exist, write a new visit method on `ParseDiagnosticsGenerator`.
 6. In that visitation method, detect the pattern for which the improved diagnostic should be emitted and emit it using `diagnostics.append`.
 7. Mark the missing or garbage nodes that are covered by the new diagnostic as handled by adding their `SyntaxIdentifier`s to `handledNodes`.
 8. If the diagnostic produces Fix-Its assert that they are generated by adding the Fix-It's message to the `DiagnosticSpec` with the `fixIt` parameter and asserting that applying the Fix-Its produces the correct source code by adding the `fixedSource` parameter to `assertParse`.
 
-> 💡 Tip: To make typing the marker emojis more convienient. you can set up code snippets in Xcode. To do this, perform the following steps:
+> 💡 Tip: To make typing the marker emojis more convenient. you can set up code snippets in Xcode. To do this, perform the following steps:
 > 1. Type the marker in any Xcode window or find it in some test case
 > 2. Select the emoji, right-click it and select “Create Code Snippet…”
 > 3. Replace “My Code Snippet” by the emoji marker character and in for “Availability” select “Comment or String”

Sources/SwiftSyntax/Documentation.docc/Glossary.md

@@ -13,7 +13,7 @@ To avoid ongoing repetition of common long terms, SwiftSyntax uses a couple of a
 
 **Expr** Abbreviation for *Expression*
 
-**Layout Node** A layout node has can have an arbitrary number of children and provides structure to the syntax tree. All ``Syntax`` nodes that aren’t ``TokenSyntax`` are layout nodes. For example a ``StructDeclSyntax`` consists of, among others, of the `struct` keyword, the name and the `memberBlock`. The latter is again a layout node that contains multiple children. Layout nodes never represent any source code in the syntax tree by themselves. All source code within the syntax tree is represented by *tokens*.
+**Layout Node** A layout node can have an arbitrary number of children and provides structure to the syntax tree. All ``Syntax`` nodes that aren’t ``TokenSyntax`` are layout nodes. For example a ``StructDeclSyntax`` consists of, among others, of the `struct` keyword, the name and the `memberBlock`. The latter is again a layout node that contains multiple children. Layout nodes never represent any source code in the syntax tree by themselves. All source code within the syntax tree is represented by *tokens*.
 
 **Node** A *layout node* or *token*