Fix: typos (#2361)

docs/src/pages/docs/cli.md

@@ -102,7 +102,7 @@ anchor deploy
 Deploys all programs in the workspace to the configured cluster.
 
 {% callout title="Tip" %}
-This is different from the `solana program deploy` command, because everytime it's run
+This is different from the `solana program deploy` command, because every time it's run
 it will generate a _new_ program address.
 {% /callout %}
 
@@ -122,7 +122,7 @@ If run with the `--program-name` option, expand only the given program.
 
 The `idl` subcommand provides commands for interacting with interface definition files.
 It's recommended to use these commands to store an IDL on chain, at a deterministic
-address, as a function of nothing but the the program's ID. This
+address, as a function of nothing but the program's ID. This
 allows us to generate clients for a program using nothing but the program ID.
 
 ### Idl Init

docs/src/pages/docs/installation.md

@@ -16,7 +16,7 @@ We recommend reading chapters 1-9 of the [Rust book](https://doc.rust-lang.org/b
 Go [here](https://docs.solana.com/cli/install-solana-cli-tools) to install Solana and then run `solana-keygen new` to create a keypair at the default location. Anchor uses this keypair to run your program tests.
 
 {% callout title="You should know!" %}
-We also recommend checking out the the official [Solana developers page](https://solana.com/developers).
+We also recommend checking out the official [Solana developers page](https://solana.com/developers).
 {% /callout %}
 
 ## Yarn

docs/src/pages/docs/manifest.md

@@ -69,7 +69,7 @@ Sets the paths --relative to the `Anchor.toml`--
    to all programs in the local
    workspace, i.e., the path to the `Cargo.toml` manifest associated with each
    program that can be compiled by the `anchor` CLI. For programs using the
-   standard Anchor workflow, this can be ommitted. For programs not written in Anchor
+   standard Anchor workflow, this can be omitted. For programs not written in Anchor
    but still want to publish, this should be added.
 
 Example:

docs/src/pages/docs/publishing-source.md

@@ -57,7 +57,7 @@ Here there are four sections.
    to all programs in the local
    workspace, i.e., the path to the `Cargo.toml` manifest associated with each
    program that can be compiled by the `anchor` CLI. For programs using the
-   standard Anchor workflow, this can be ommitted. For programs not written in Anchor
+   standard Anchor workflow, this can be omitted. For programs not written in Anchor
    but still want to publish, this should be added.
 3. `[provider]` - configures the wallet and cluster settings. Here, `mainnet` is used because the registry only supports `mainnet` binary verification at the moment.
 4. `[programs.mainnet]` - configures each program in the workpace, providing