[docs] Fix broken links (#17566)

* [docs] Fix broken links

* Fix the charactor

* Update the charactor

1 files changed, 3 insertions, 3 deletions

diff --git a/docs/users/versioning.implementation-details.md b/docs/users/versioning.implementation-details.md
index fc5981e24..02645ec81 100644
--- a/docs/users/versioning.implementation-details.md
+++ b/docs/users/versioning.implementation-details.md
@@ -83,7 +83,7 @@ To compute an installation plan, vcpkg follows roughly these steps:
         * If there is a previous version selected:

             * If the versioning scheme of the new constraint does not match that of the previously selected version:

                 * Add a version conflict.

-            * If the constraint’s version is not comparable to the previously selected version. For example, comparing “version-string: apple” to “version-string: orange”:

+            * If the constraint's version is not comparable to the previously selected version. For example, comparing "version-string: apple" to "version-string: orange":

                 * Add a version conflict.

             * If the constraints version is higher than the previously selected version:

                 * Select the highest version.

@@ -102,7 +102,7 @@ With the introduction of versioning constraints, it is now possible that a packa
 

 To solve this problem, a new set of metadata files was introduced. These files are located in the `versions/` directory at the root level of the vcpkg repository.

 

-The `versions/` directory, will contain JSON files for each one of the ports available in the registry. Each file will list all the versions available for a package and contain a Git tree-ish object that vcpkg can check out to obtain that version’s portfiles.

+The `versions/` directory, will contain JSON files for each one of the ports available in the registry. Each file will list all the versions available for a package and contain a Git tree-ish object that vcpkg can check out to obtain that version's portfiles.

 

 Example: `zlib.json`

 

@@ -129,6 +129,6 @@ Example: `zlib.json`
 }

 ```

 

-For each port, its corresponding versions file should be located in `versions/{first letter of port name}-/{port name}.json`. For example, zlib’s version file will be located in `versions/z-/zlib.json`. Aside from port version files, the current baseline file is located in `versions/baseline.json`.

+For each port, its corresponding versions file should be located in `versions/{first letter of port name}-/{port name}.json`. For example, zlib's version file will be located in `versions/z-/zlib.json`. Aside from port version files, the current baseline file is located in `versions/baseline.json`.