Merge pull request #40872 from philipturner/patch-1

Author: swift-ci

docs/DebuggingTheCompiler.md

@@ -931,7 +931,7 @@ standalone driver must be built as a separate build product using the
 *just-built* Swift compiler and toolchain (the ones built in the same
 `build-script` invocation, preceding the SwiftDriver build product). The
 additional build product is added to the build by specifying the
-`--swift-driver` option of the `build-script`. The driver product is istalled
+`--swift-driver` option of the `build-script`. The driver product is installed
 into the resulting toolchain installation by specifying the
 `--install-swift-driver` option of the `build-script`.
 

docs/HowToGuides/GettingStarted.md

@@ -457,7 +457,7 @@ There are two main ways to run tests:
    The `-s` and `-vv` flags print a progress bar and the executed commands
    respectively.
 
-If you making small changes to the compiler or some other component, you'll
+If you are making small changes to the compiler or some other component, you'll
 likely want to [incrementally rebuild](#editing-code) only the relevant
 Ninja/Xcode target and use `lit.py` with `--filter`. One potential failure
 mode with this approach is accidental use of stale binaries. For example, say