[doc] Fix spelling errors (#17560)

* [doc] Fix spelling errors in docs

* [doc] Fix spelling errors in scripts

* Bump version

* x-add-version

* Fix another typo

* Rebuild

4 files changed, 5 insertions, 5 deletions

diff --git a/docs/specifications/prefab.md b/docs/specifications/prefab.md
index f94758b49..8b8487442 100644
--- a/docs/specifications/prefab.md
+++ b/docs/specifications/prefab.md
@@ -50,7 +50,7 @@ Note:
 ./vcpkg export --triplet x64-android jsoncpp --prefab --prefab-maven --prefab-debug
 ```
 
-You will see an ouput like this:
+You will see an output like this:
 ```
 The following packages are already built and will be exported:
     jsoncpp:arm64-android
@@ -102,7 +102,7 @@ In gradle.properties
     android.enableParallelJsonGen=false
     android.prefabVersion=${prefab.version}
 
-Successfuly exported jsoncpp. Checkout .../vcpkg/prefab 
+Successfully exported jsoncpp. Checkout .../vcpkg/prefab 
 
 ```
 
diff --git a/docs/specifications/registries-2.md b/docs/specifications/registries-2.md
index 46429db70..b44dacfe5 100644
--- a/docs/specifications/registries-2.md
+++ b/docs/specifications/registries-2.md
@@ -459,7 +459,7 @@ This means that, even across different machines, the same registries will be use
 We will also be able to write down version resolution in this file as soon as that feature is added.
 
 It is recommended that one adds this `vcpkg-lock.json` to one's version control.
-This file is machine generated, and it is not specified how it's layed out;
+This file is machine generated, and it is not specified how it's laid out;
 however, for purposes of this RFC, we will define how it relates to git registries.
 
 In `vcpkg-lock.json`, in the top level object,
diff --git a/docs/specifications/registries.md b/docs/specifications/registries.md
index 426593829..896188f4c 100644
--- a/docs/specifications/registries.md
+++ b/docs/specifications/registries.md
@@ -182,7 +182,7 @@ and then run the following algorithm on each dependency:
 
 vcpkg will also rerun this algorithm whenever an install is run with different configuration.
 
-### How Registries are Layed Out
+### How Registries are Laid Out
 
 There are three kinds of registries, but they only differ in how the registry gets onto one's filesystem.
 Once the registry is there, package lookup runs the same, with each kind having it's own way of defining its
diff --git a/docs/specifications/versioning.md b/docs/specifications/versioning.md
index e8122c359..1ad9ef8dc 100644
--- a/docs/specifications/versioning.md
+++ b/docs/specifications/versioning.md
@@ -32,7 +32,7 @@ This feature requires the use of manifests to declare project dependencies. To a
 * Ability for a top-level manifest to override all other version constraints.

 * Ability to declare a baseline for all versions.

 

-Example: A manifeset (`vcpkg.json`) using versioning features.

+Example: A manifest (`vcpkg.json`) using versioning features.

 ```json

 {

   "name": "versions-test",