Misc wording updates

Author: MichaelSimons

Documentation/eliminating-pre-builts.md

@@ -7,7 +7,7 @@ organization.
 ## Table of content
 
 - [What is a Prebuilt](#what-is-a-prebuilt)
-- [Elimitating pre-builts](#eliminating-pre-builts)
+- [Eliminating pre-builts](#eliminating-pre-builts)
 - [Allowed exceptions](#allowed-exceptions)
 - [Contacts](#contacts)
 
@@ -28,7 +28,7 @@ When onboarding a repository to source-build or adding a new dependency to a
 source-buildable one, the contributor runs the risk of introducing a new
 pre-built to the product. To protect against this and catch any new pre-builts
 as soon as possible, Arcade source-build infrastructure provides _pre-built
-detection_ - MSBuild logic responsible for veryfing that no used dependency is a
+detection_ - MSBuild logic responsible for verifying that no used dependency is a
 pre-built. In case one is discovered (for example, during a PR pipeline), the
 build will fail with an appropriate message somewhat similar to the following:
 
@@ -48,12 +48,12 @@ from pre-built detection will be flagged as pre-builts.
 
 ## Eliminating pre-builts
 
-When altering the dependecy tree of a repository, specifically adding or
-updating dependencies, there is a posibility that a new pre-built is introduced,
+When altering the dependency tree of a repository, specifically adding or
+updating dependencies, there is a possibility that a new pre-built is introduced,
 failing the build and blocking any merge. This can be resolved by identifying
-what exactly is the pre-built and following the approriate steps listed below.
+what exactly is the pre-built and following the appropriate steps listed below.
 
-To check if new pre-builts were introduce, the repository needs to be
+To check if new pre-builts were introduced, the repository needs to be
 source-built first. This can be done through the following command:
 
 ```sh
@@ -75,7 +75,7 @@ pre-built.
 
 ### Pre-built through a transitive dependency
 
-During a project dependency updated, a new pre-built might be introduced by a
+During a project dependency update, a new pre-built might be introduced by a
 new or updated transitive dependency. While the Arcade tooling will highlight
 the name and version of the pre-built in the build exception as well as the
 project that restored the dependency in question, it will not point out where
@@ -86,7 +86,7 @@ dependency, it might be hard to identify the relationship that is bringing in
 the pre-built into the project, especially if the developer has limited
 knowledge of the project or code-base in general.
 
-Arcade source-build infrastructure helps accomplish this this by pointing out
+Arcade source-build infrastructure helps accomplish this by pointing out
 the `project.assets.json` file that is referencing the pre-built in the
 `./artifacts/source-build/self/prebuild-report/prebuild-usage.xml` report file.
 A `project.assets.json` file is a NuGet restore process artifact that contains a
@@ -145,12 +145,12 @@ dependency causing the `System.Text.Json` pre-built.
 The list of permitted pre-builts can be found in the `./eng/SourceBuildPrebuiltBaseline.xml` file in the root of the repository.
 It contains package information of pre-builts that for one reason or another are allowed in the source-build of the repository.
 
-Any new addition to the pre-built exception list must be signed-off by a member of the `@dotnet/source-build` team.
+Any new additions to the pre-built exception list must be signed-off by a member of the `@dotnet/source-build` team.
 
 In cases where a specific package needs to be excluded from pre-built detection
 (for example, to not block the introduction of changes until a source-build
 acceptable solution for the pre-built is provided), the developer can directly
-specify the name / version of the depedency:
+specify the name / version of the dependency:
 
 ```xml
 <UsageData>