docs: fix typos

README.md

@@ -87,7 +87,7 @@ cd testnet/stacks-node
 cargo run --bin stacks-node -- start --config ./conf/testnet-follower-conf.toml
 ```
 
-_On Windows, many tests will fail if the line endings aren't `LF`. Please ensure that you are have git's `core.autocrlf` set to `input` when you clone the repository to avoid any potential issues. This is due to the Clarity language currently being sensitive to line endings._
+_On Windows, many tests will fail if the line endings aren't `LF`. Please ensure that you have git's `core.autocrlf` set to `input` when you clone the repository to avoid any potential issues. This is due to the Clarity language currently being sensitive to line endings._
 
 Additional testnet documentation is available [here](./docs/testnet.md) and [here](https://docs.stacks.co/docs/nodes-and-miners/miner-testnet)
 

docs/ci-release.md

@@ -23,7 +23,7 @@ All releases are built via a Github Actions workflow named `CI` ([ci.yml](../.gi
   - `stacks-core:<default-branch-name>`
 - An untagged build of any branch will produce a single image built from source on Debian with glibc:
   - `stacks-core:<branch-name>`
-- A tagged release on a non-default branch will produces:
+- A tagged release on a non-default branch will produce:
   - Docker Alpine image for several architectures tagged with:
     - `stacks-core:<x.x.x.x.x>`
   - Docker Debian image for several architectures tagged with:
@@ -83,7 +83,7 @@ There are also 2 different methods in use with regard to running tests:
 A matrix is used when there are several known tests that need to be run. Partitions (shards) are used when there is a large and unknown number of tests to run (ex: `cargo test` to run all tests).
 
 There is also a workflow designed to run tests that are manually triggered: [Standalone Tests](../.github/workflows/standalone-tests.yml).
-This workflow requires you to select which test(s) you want to run, which then triggers a reusbale workflow via conditional. For example, selecting "Epoch Tests" will run the tests defined in [Epoch Tests](../.github/workflows/epoch-tests.yml). Likewise, selecting `Release Tests` will run the same tests as a release workflow.
+This workflow requires you to select which test(s) you want to run, which then triggers a reusable workflow via conditional. For example, selecting "Epoch Tests" will run the tests defined in [Epoch Tests](../.github/workflows/epoch-tests.yml). Likewise, selecting `Release Tests` will run the same tests as a release workflow.
 
 Files:
 

docs/rpc-endpoints.md

@@ -111,7 +111,7 @@ Returns a JSON list containing the following:
 ```
 
 The `consensus_hash` field identifies the sortition in which the given block was
-chosen.  The `header` is the raw block header, a a hex string.  The
+chosen.  The `header` is the raw block header, a hex string.  The
 `parent_block_id` is the block ID hash of this block's parent, and can be used
 as a `?tip=` query parameter to page through deeper and deeper block headers.
 
@@ -143,8 +143,8 @@ Returns JSON data in the form:
 }
 ```
 
-Where balance is the hex encoding of a unsigned 128-bit integer
-(big-endian), nonce is a unsigned 64-bit integer, and the proofs are
+Where balance is the hex encoding of an unsigned 128-bit integer
+(big-endian), nonce is an unsigned 64-bit integer, and the proofs are
 provided as hex strings.
 
 For non-existent accounts, this _does not_ 404, rather it returns an
@@ -212,7 +212,7 @@ JSON object _without_ the `proof` field.
 
 ### GET /v2/fees/transfer
 
-Get an estimated fee rate for STX transfer transactions. This a a fee rate / byte, and is returned as a JSON integer.
+Get an estimated fee rate for STX transfer transactions. This is a fee rate / byte, and is returned as a JSON integer.
 
 ### GET /v2/contracts/interface/[Stacks Address]/[Contract Name]
 
@@ -530,6 +530,6 @@ Return metadata about the highest-known tenure, as the following JSON structure:
 
 Here, `consensus_hash` identifies the highest-known tenure (which may not be the
 highest sortition), `reward_cycle` identifies the reward cycle number of this
-tenure, `tip_block_id` idenitifies the highest-known block in this tenure, and
+tenure, `tip_block_id` identifies the highest-known block in this tenure, and
 `tip_height` identifies that block's height.