docs: fixes typos (#1714)

CONTRIBUTING.md

@@ -25,7 +25,7 @@ If you want to make changes, please read [the Build page](./docs/howto-build.md)
 
 ### Building VSCodium
 
-To build VSCOdium, please follow the command found in the section [`Build Scripts`](./docs/howto-build.md#build-scripts).
+To build VSCodium, please follow the command found in the section [`Build Scripts`](./docs/howto-build.md#build-scripts).
 
 ### Updating patches
 
@@ -33,9 +33,9 @@ If you want to update the existing patches, please follow the section [`Patch Up
 
 ### Add a new patch
 
-- firstly, you need to build VSCodium
+- first, you need to build VSCodium
 - then use the command `patch.sh <your patch name>`, to initiate a new patch
-- when the script pause at `Press any key when the conflict have been resolved...`, open `vscode` directory in **VSCodium**
+- when the script pauses at `Press any key when the conflict have been resolved...`, open `vscode` directory in **VSCodium**
 - run `yarn watch`
 - run `./script/code.sh`
 - make your changes

docs/accounts-authentication.md

@@ -2,15 +2,15 @@
 
 ## GitHub
 
-The GitHub authentication has been patched to use personal access token.
+The GitHub authentication has been patched to use personal access tokens.
 
-Here how to create a new personal access token: https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token
+Here is how to create a new personal access token: https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token
 
 ## Microsoft
 
 The Microsoft authentication hasn't been patched so its status is unknown.
 
-## When does it happened?
+## When does it happen?
 
 An account authentication occurs only when an extension is asking for it.
 

docs/howto-build.md

@@ -50,7 +50,7 @@
 - 7z
 - [WiX Toolset](http://wixtoolset.org/releases/)
 - python3
-- 'Tools for Native Modules' from official Node.js installer
+- 'Tools for Native Modules' from hte official Node.js installer
 
 ## <a id="build-scripts"></a>Build Scripts
 
@@ -64,7 +64,7 @@ A build helper script can be found at `build/build.sh`.
 
 The `insider` version can be built with `./build/build.sh -i` on the `insider` branch.
 
-You can try the lastest version with the command `./build/build.sh -il` but the patches might not be up to date.
+You can try the latest version with the command `./build/build.sh -il` but the patches might not be up to date.
 
 ## <a id="build-docker"></a>Build in Docker
 
@@ -131,10 +131,10 @@ review-tools.snap-review --allow-classic codium*.snap
 
 - run `./build/build_<os>.sh`, if a patch is failing then,
 - run `./build/update_patches.sh`
-- when the script pause at `Press any key when the conflict have been resolved...`, open `vscode` directory in **VSCodium**
+- when the script pauses at `Press any key when the conflict have been resolved...`, open `vscode` directory in **VSCodium**
 - fix all the `*.rej` files
 - run `yarn watch`
-- run `./script/code.sh` until everything ok
+- run `./script/code.sh` until everything is ok
 - press any key to continue the script `update_patches.sh`
 
 ## <a id="patch-update-process-manual"></a>Manual
@@ -145,5 +145,5 @@ review-tools.snap-review --allow-classic codium*.snap
 - run `git apply --reject ../patches/<name>.patch`
 - fix all the `*.rej` files
 - run `yarn watch`
-- run `./script/code.sh` until everything ok
+- run `./script/code.sh` until everything is ok
 - run `git diff > ../patches/<name>.patch`

docs/index.md

@@ -96,7 +96,7 @@ with the content:
 
 ### <a id="howto-selfhost-marketplace"></a>How to self-host your own extension gallery
 
-Individual developers and enterprise companies in regulated or security-conscious industries can self-host their own extension gallery. In all of these cases you'd enter its endpoint URLs as noted above, replacing `marketplace.visualstudio.com` with `your-self-hosted-marketplace-address.example.com` (or IP address), setting `cacheUrl` / `VSCODE_GALLERY_CACHE_URL` to an empty string.
+Individual developers and enterprise companies in regulated or security-conscious industries can self-host their own extension gallery. In all of these cases, you'd enter its endpoint URLs as noted above, replacing `marketplace.visualstudio.com` with `your-self-hosted-marketplace-address.example.com` (or IP address), setting `cacheUrl` / `VSCODE_GALLERY_CACHE_URL` to an empty string.
 
 There are likely other options, but the following were reported to work:
 
@@ -164,7 +164,7 @@ To copy your settings manually:
 
 In VSCodium, `Sign in with GitHub` is using a Personal Access Token.<br />
 Follow the documentation https://docs.github.com/en/github/authenticating-to-github/creating-a-personal-access-token to create your token.<br />
-Select the scopes dependending of the extension which need access to GitHub. (GitLens requires the `repo` scope.)
+Select the scopes dependending on the extension which needs access to GitHub. (GitLens requires the `repo` scope.)
 
 ### Linux
 
@@ -177,7 +177,7 @@ You can follow the [Portable Mode instructions](https://code.visualstudio.com/do
 
 ## <a id="file-manager"></a>How do I fix the default file manager (Linux)?
 
-In some case, VSCodium becomes the file manager used to open directories (instead of apps like Dolphin or Nautilus).<br />
+In some cases, VSCodium becomes the file manager used to open directories (instead of apps like Dolphin or Nautilus).<br />
 It's due to that no application was defined as the default file manager and so the system is using the latest capable application.
 
 To set the default app, create the file `~/.config/mimeapps.list` with the content like:

docs/troubleshooting.md

@@ -30,13 +30,13 @@ Install these packages on Fedora:
 * dbus-glib-devel
 * libdbusmenu
 
-On Ubuntu this package called `libdbusmenu-glib4`.
+On Ubuntu this package is called `libdbusmenu-glib4`.
 
 Credits: [Gerson](https://gitlab.com/paulcarroty/vscodium-deb-rpm-repo/-/issues/91)
 
 ## <a id="macos"></a>macOS
 
-Since the App is signed with self-signed certificate, on the first launch, you might see the following messages:
+Since the App is signed with a self-signed certificate, on the first launch, you might see the following messages:
 
 #### <a id="macos-unidentified-developer"></a>*App can't be opened because Apple cannot check it for malicious software*