Fix typos in documentation (ordinals#2328)

* fix typos

README.md

@@ -40,7 +40,7 @@ This address is 2 of 4 multisig wallet with keys held by
 [rodarmor](https://twitter.com/rodarmor), and
 [ordinally](https://twitter.com/veryordinally).
 
-Bitcoin received will go towards funding maintainance and development of `ord`,
+Bitcoin received will go towards funding maintenance and development of `ord`,
 as well as hosting costs for [ordinals.com](https://ordinals.com).
 
 Thank you for donating!
@@ -141,7 +141,7 @@ cargo test --all
 cargo test --all -- --ignored
 ```
 
-Have look at the [justfile](justfile) to see some more helpful recipes
+Have a look at the [justfile](justfile) to see some more helpful recipes
 (commands). Here are a couple more good ones:
 
 ```
@@ -174,7 +174,7 @@ See `ord --help` for details.
 `bitcoind` RPC Authentication
 -----------------------------
 
-`ord` makes RPC calls to `bitcoind`, which usually require a username and
+`ord` makes RPC calls to `bitcoind`, which usually requires a username and
 password.
 
 By default, `ord` looks a username and password in the cookie file created by

docs/src/contributing.md

@@ -36,7 +36,7 @@ Ideas for small issues:
 - Find an issue that needs more research, and do that research and summarize it
   in a comment
 - Find an out-of-date issue and comment that it can be closed
-- Find an issue that shouldn't be done, and provide constrictive feedback
+- Find an issue that shouldn't be done, and provide constructive feedback
   detailing why you think that is the case
 
 Merge early and often
@@ -49,7 +49,7 @@ test. Do research or testing, and report on your results. Break a feature into
 small sub-features, and implement them one at a time.
 
 Figuring out how to break down a larger PR into smaller PRs where each can be
-merged is a art form well-worth practicing. The hard part is that each PR must
+merged is an art form well-worth practicing. The hard part is that each PR must
 itself be an improvement.
 
 I strive to follow this advice myself, and am always better off when I do.

docs/src/donate.md

@@ -14,7 +14,7 @@ Both addresses are in a 2 of 4 multisig wallet with keys held by
 [rodarmor](https://twitter.com/rodarmor), and
 [ordinally](https://twitter.com/veryordinally).
 
-Donations received will go towards funding maintainance and development of `ord`,
+Donations received will go towards funding maintenance and development of `ord`,
 as well as hosting costs for [ordinals.com](https://ordinals.com).
 
 Thank you for donating!

docs/src/faq.md

@@ -4,7 +4,7 @@ Ordinal Theory FAQ
 What is ordinal theory?
 -----------------------
 
-Ordinal theory is is a protocol for assigning serial numbers to satoshis, the
+Ordinal theory is a protocol for assigning serial numbers to satoshis, the
 smallest subdivision of a bitcoin, and tracking those satoshis as they are
 spent by transactions.
 
@@ -268,7 +268,7 @@ features like globally unique symbols and enhanced provenance.
 *Inscriptions do not support on-chain royalties.* This is negative, but only
 depending on how you look at it. On-chain royalties have been a boon for
 creators, but have also created a huge amount of confusion in the Ethereum NFT
-ecosystem. The ecosystem now grapples with this issue, and is is engaged in a
+ecosystem. The ecosystem now grapples with this issue, and is engaged in a
 race to the bottom, towards a royalties-optional future. Inscriptions have no
 support for on-chain royalties, because they are technically infeasible. If you
 choose to create inscriptions, there are many ways you can work around this

docs/src/inscriptions.md

@@ -54,7 +54,7 @@ First the string `ord` is pushed, to disambiguate inscriptions from other uses
 of envelopes.
 
 `OP_PUSH 1` indicates that the next push contains the content type, and `OP_PUSH
-0`indicates that subsequent data pushes contain the content itself. Multiple data
+0` indicates that subsequent data pushes contain the content itself. Multiple data
 pushes must be used for large inscriptions, as one of taproot's few
 restrictions is that individual data pushes may not be larger than 520 bytes.
 

docs/src/overview.md

@@ -72,7 +72,7 @@ naturally lend themselves to a system of rarity. These periodic events are:
 - *Cycles*: Every six halvings, something magical happens: the halving and the
   difficulty adjustment coincide. This is called a conjunction, and the time
   period between conjunctions a cycle. A conjunction occurs roughly every 24
-  years. The first conjunction should happen some time in 2032.
+  years. The first conjunction should happen sometime in 2032.
 
 This gives us the following rarity levels:
 
@@ -102,7 +102,7 @@ Now for some examples. This satoshi is common:
 ```
 1°1′1″1‴
 │ │ │ ╰─ Not first sat in block
-│ │ ╰─── Not first block in difficutly adjustment period
+│ │ ╰─── Not first block in difficulty adjustment period
 │ ╰───── Not first block in halving epoch
 ╰─────── Second cycle
 ```
@@ -113,7 +113,7 @@ This satoshi is uncommon:
 ```
 1°1′1″0‴
 │ │ │ ╰─ First sat in block
-│ │ ╰─── Not first block in difficutly adjustment period
+│ │ ╰─── Not first block in difficulty adjustment period
 │ ╰───── Not first block in halving epoch
 ╰─────── Second cycle
 ```
@@ -163,7 +163,7 @@ from above:
 
 ```
 1°1′1″
-│ │ ╰─ Not first block in difficutly adjustment period
+│ │ ╰─ Not first block in difficulty adjustment period
 │ ╰─── Not first block in halving epoch
 ╰───── Second cycle
 ```
@@ -203,7 +203,7 @@ the unspendable genesis block.
 
 As an example, 1905530482684727°'s name is "iaiufjszmoba". The name of the last
 satoshi to be mined is "a". Every combination of 10 characters or less is out
-there, or will be out there, some day.
+there, or will be out there, someday.
 
 Exotics
 -------
@@ -253,7 +253,7 @@ ordinals were independently discovered on at least two separate occasions, long
 before the era of modern NFTs began.
 
 On August 21st, 2012, Charlie Lee [posted a proposal to add proof-of-stake to
-Bitcoin to the Bitocin Talk
+Bitcoin to the Bitcoin Talk
 forum](https://bitcointalk.org/index.php?topic=102355.0). This wasn't an asset
 scheme, but did use the ordinal algorithm, and was implemented but never
 deployed.