fix: typos in documentation files (#1923)

* Update README.md

* Update CUSTOM_PROTOBUF_CODECS.md

* Update TEST_VECTORS.md

* [autofix.ci] apply automated fixes

---------

Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>

Author: viktorking7

packages/faucet/README.md

@@ -95,8 +95,8 @@ as soon as there is
 ### Working with docker
 
 **Note:** The Dockerfile in this repo is for demonstration purposes only. If you
-chose to deploy the faucet via docker, make sure to copy the Dockerfile and keep
-it up-to-date.
+choose to deploy the faucet via docker, make sure to copy the Dockerfile and
+keep it up-to-date.
 
 - Build an artifact (from monorepo root)
 
@@ -139,7 +139,7 @@ curl --header "Content-Type: application/json" \
   http://localhost:8000/credit
 ```
 
-### Checking the faucets status
+### Checking the faucet's status
 
 The faucet provides a simple status check in the form of an http GET request. As
 above, make sure to adjust the URL as necessary.

packages/proto-signing/TEST_VECTORS.md

@@ -55,15 +55,15 @@ This uses the testgen mnemonic:
 ## Create the transactions
 
 First we create the unsigned transaction template we will be signing. We want to
-use the same flags as the testvectors create manually.
+use the same flags as the test vectors created manually.
 
 ```
 ./build/simd tx bank send --generate-only --chain-id simd-testing --fees 2000ucosm $(./build/simd keys show -a testgen) cosmos1qypqxpq9qcrsszg2pvxq6rs0zqg3yyc5lzv7xu 1234567ucosm > unsigned_tx.json
 ```
 
 This is what I get from `jq . unsigned_tx.json`, which is slightly different
-that the current test vector, in that I added a non-empty fee amount to properly
-test that:
+from the current test vector because I added a non-empty fee amount to properly
+test that case:
 
 ```json
 {

packages/stargate/CUSTOM_PROTOBUF_CODECS.md

@@ -92,7 +92,7 @@ and
 ### Step 3
 
 In Step 2 we saw how the codec is generated (i.e. the TypeScript code
-generation). Now we look into using this codec. This section is split in
+generation). Now we look into using this codec. This section is split into
 
 - Step 3a: custom messages
 - Step 3b: custom queries