Fixing spelling errors found by Vale (ipfs#1358)

Author: TMoMoreau

docs/basics/README.md

@@ -21,4 +21,4 @@ If you're a bit more serious about IPFS and want to start poking around the comm
 
 ## Other implementations
 
-There are many other IPFS implementations than the onramps discussed above.  [Check them out here!](./ipfs-implementations.md)
+There are many other IPFS implementations than the on-ramps discussed above.  [Check them out here!](./ipfs-implementations.md)

docs/basics/ipfs-implementations.md

@@ -1,6 +1,6 @@
 ---
 title: "IPFS implementations"
-description: "There isn't one canonical IPFS implemetnation. Learn about the various IPFS implementations available for different usecases."
+description: "There isn't one canonical IPFS implementation. Learn about the various IPFS implementations available for different use cases."
 ---
 
 # IPFS implementations
@@ -18,15 +18,15 @@ Relevant specifications are listed in [ipfs/specs](https://github.com/ipfs/specs
 | Agregore         | <https://github.com/AgregoreWeb/agregore-ipfs-daemon>                   | go, javascript         | Mobile friendly Kubo daemon.                                                                                             |
 | barge            | <https://github.com/application-research/estuary/tree/master/cmd/barge> | go                     | CLI tool with a git like workflow to upload deltas to estuary.                                                           |
 | Boost            | <https://github.com/filecoin-project/boost>                             | go                     | Daemon to get IPFS data in and out of a Filecoin storage provider.                                                       |
-| Elastic provider | <https://github.com/ipfs-elastic-provider/ipfs-elastic-provider>        | javascript, typescript | Scallable Cloud-Native implementation.                                                                                   |
+| Elastic provider | <https://github.com/ipfs-elastic-provider/ipfs-elastic-provider>        | javascript, typescript | Scalable Cloud-Native implementation.                                                                                   |
 | Estuary          | <https://github.com/application-research/estuary/>                      | go                     | Daemon oriented service to pin and onboard IPFS data into Filecoin.                                                      |
-| gomobile-ipfs    | <https://github.com/ipfs-shipyard/gomobile-ipfs>                        | go                     | Library oriented ipfs daemon to help embeding Kubo into a mobile app.                                                   |
-| ipfs cluster     | <https://github.com/ipfs/ipfs-cluster>                                  | go                     | CRDT / Raft consensus between some more less trusted nodes to allocate and synchronise a pinset on multiple IPFS nodes.  |
+| gomobile-ipfs    | <https://github.com/ipfs-shipyard/gomobile-ipfs>                        | go                     | Library oriented ipfs daemon to help embedding Kubo into a mobile app.                                                   |
+| ipfs cluster     | <https://github.com/ipfs/ipfs-cluster>                                  | go                     | CRDT / Raft consensus between some more less trusted nodes to allocate and synchronize a pinset on multiple IPFS nodes.  |
 | ipfs tiny        | <https://gitlab.com/librespacefoundation/ipfs-tiny>                     | c++                    | Tiny embeddable, os-independent IPFS implementation.                                                                     |
 | ipfs-embed       | <https://github.com/ipfs-rust/ipfs-embed>                               | rust                   | Small embeddable ipfs implementation.                                                                                    |
 | ipfs-lite        | <https://github.com/hsanjuan/ipfs-lite>                                 | go                     | Minimal library oriented ipfs daemon building on the same blocks as Kubo but with a minimal glue layer.                 |
 | ipfs-nucleus     | <https://github.com/peergos/ipfs-nucleus/>                              | go                     | Minimal IPFS replacement for P2P IPLD apps.                                                                              |
-| ipget            | <https://github.com/ipfs/ipget>                                         | go                     | Minimal wget insipired tool to download files from IPFS nodes over bitswap.                                              |
+| ipget            | <https://github.com/ipfs/ipget>                                         | go                     | Minimal wget inspired tool to download files from IPFS nodes over bitswap.                                              |
 | iroh             | <https://github.com/n0-computer/iroh>                                   | rust                   | Extreme-Efficiency oriented IPFS implementation.                                                                         |
 | js-ipfs          | <https://github.com/ipfs/js-ipfs>                                       | javascript, typescript | Javascript implementation targeting nodejs and browsers.                                                                 |
 | Kubo             | <https://github.com/ipfs/kubo>                                          | go                     | Generalist daemon oriented IPFS implementation with an extensive HTTP API.                                               |

docs/community/chat.md

@@ -13,7 +13,7 @@ Join the [IPFS Discord server](https://discord.gg/ipfs) for synchronous chat! [S
 
 ## Matrix
 
-Join the [Matrix space](https://matrix.to/#/#ipfs-space:ipfs.io). [Homeserver documentation is available on Notion](https://pl-strflt.notion.site/IPFS-Matrix-Homeserver-Documentation-31481e76843547b7ab5160a87eed2b9f).
+Join the [Matrix space](https://matrix.to/#/#ipfs-space:ipfs.io). [Home server documentation is available on Notion](https://pl-strflt.notion.site/IPFS-Matrix-Homeserver-Documentation-31481e76843547b7ab5160a87eed2b9f).
 
 ## Slack
 

docs/community/contribute/grammar-formatting-and-style.md

@@ -212,7 +212,7 @@ List items end with a period `.`, or a colon `:` if the list item has a sub-list
    3. David Copperfield.
 2. J.R.R Tolkien non-fiction books:
    1. The Hobbit.
-   2. Silmarillion.
+   2. The Silmarillion.
    3. Letters from Father Christmas.
 
 ##### Unordered lists

docs/community/contribute/ways-to-contribute.md

@@ -9,7 +9,7 @@ So you want to contribute to IPFS and the ecosystem? Here is a quick listing of
 
 ## Code
 
-IPFS and its sister-projects are big, with lots of code written in multiple languages. We always need help writing and maintaining code, but it can be daunting to just jump in. We use the label _Help Wanted_ on features or bugfixes that people can help out with. They are an excellent place for you to start contributing code.
+IPFS and its sister-projects are big, with lots of code written in multiple languages. We always need help writing and maintaining code, but it can be daunting to just jump in. We use the label _Help Wanted_ on features or bug fixes that people can help out with. They are an excellent place for you to start contributing code.
 
 The biggest and most active repositories we have today are:
 

docs/community/contribute/writing-guide.md

@@ -31,7 +31,7 @@ The end goal of a walkthrough is for the reader to achieve a very particular fun
 
 #### Short length
 
-Since walkthroughs cover one particular function or process, they tend to be quite short. The estimated reading time of a walkthrough is somewhere between 2 and 10 minutes. Most of the time, the most critical content in a walkthrough is presented in a numbered list. Images and gifs can help the reader understand what they should be doing.
+Since walkthroughs cover one particular function or process, they tend to be quite short. The estimated reading time of a walkthrough is somewhere between 2 and 10 minutes. Most of the time, the most critical content in a walkthrough is presented in a numbered list. Images and GIFs can help the reader understand what they should be doing.
 
 If a walkthrough is converted into a video, that video should be no longer than 5 minutes.
 

docs/concepts/bitswap.md

@@ -25,7 +25,7 @@ IPFS breaks up files into chunks of data called _blocks_. These blocks are ident
 
 When nodes running the Bitswap protocol want to fetch a file, they send out `want-lists` to other peers. A `want-list` is a list of CIDs for blocks a peer wants to receive. Each node remembers which blocks its peers want. Each time a node receives a block, it checks if any of its peers want the block and sends it to them if they do.
 
-Here is a simplifed version of a `want-list`:
+Here is a simplified version of a `want-list`:
 
 ```javascript
 Want-list {

docs/concepts/case-study-audius.md

@@ -109,7 +109,7 @@ Audius uses the following IPFS implementations with no modification:
 - [`ipfs-http-client`](https://github.com/ipfs/js-ipfs/tree/master/packages/ipfs-http-client)
   - _Creator node is a Node.js-based service and heavily uses this client to interact with dedicated IPFS nodes_
 
-For streaming, the Audius team uses HTTP Livestreaming (HLS) on top of the IPFS core implementation. The client pre-fetches the segments as the listener streams them using HLS.
+For streaming, the Audius team uses HTTP Live Streaming (HLS) on top of the IPFS core implementation. The client pre-fetches the segments as the listener streams them using HLS.
 
 ## Audius + IPFS: the future
 

docs/concepts/case-study-likecoin.md

@@ -45,7 +45,7 @@ LikeCoin aims to fundamentally improve the way content is shared, moderated, and
 _— Kin Ko, Founder, LikeCoin_
 :::
 
-At the heart of the LikeCoin ecosystem is its decentralized metadata registry, written on [LikeCoin's own blockchain](https://github.com/likecoin/likecoin-chain). As the world's first data registry specifically recording the internet's digital creative content, it stores ISCN metadata for every item published or shared within Liker Land or associated with the LikeCoin button.
+At the heart of the LikeCoin ecosystem is its decentralized metadata registry, written on [LikeCoin's own blockchain](https://github.com/likecoin/likecoin-chain). As the world's first data registry specifically recording the Internet's digital creative content, it stores ISCN metadata for every item published or shared within Liker Land or associated with the LikeCoin button.
 
 But the LikeCoin team quickly realized that simply creating a system of record for ISCNs wasn't enough to fulfill their core goal of building a equitable publishing infrastructure. They also needed an efficient, decentralized, and censorship-resistant means to provide or reprovide the content that those ISCNs represent. The team found their solution in IPFS.
 

docs/concepts/case-study-morpheus.md

@@ -32,9 +32,9 @@ Morpheus.Network uses a private network of IPFS document storage nodes, combined
 
 ## The story
 
-Morpheus.Network unlocks potential in a previously underserved area of logistics by empowering a wide range of entities along the international supply chain to interoperate seamlessly. Securely storing and distributing the documentation required to move international shipments across borders is a tricky problem: Multiple parties, each using their own software and tools, must successfully interact in order to create, verify, and present documentation for export and import. Morpheus.Network CEO Dan Weinberger summarizes the problem space as follows: "In supply chain, there are a lot of these parts and pieces that don't speak to each other properly. We have shipping companies — whether it's ocean shipping or transport trucks — customs brokers, the various customs or border protection [agencies], and the actual shipper, seller, and buyer. All of them need to interact with each other in a seamless fashion. Right now, that's just not the case."
+Morpheus.Network unlocks potential in a previously under-served area of logistics by empowering a wide range of entities along the international supply chain to interoperate seamlessly. Securely storing and distributing the documentation required to move international shipments across borders is a tricky problem: Multiple parties, each using their own software and tools, must successfully interact in order to create, verify, and present documentation for export and import. Morpheus.Network CEO Dan Weinberger summarizes the problem space as follows: "In supply chain, there are a lot of these parts and pieces that don't speak to each other properly. We have shipping companies — whether it's ocean shipping or transport trucks — customs brokers, the various customs or border protection [agencies], and the actual shipper, seller, and buyer. All of them need to interact with each other in a seamless fashion. Right now, that's just not the case."
 
-Without the IPFS-backed document management system that Morpheus.Network offers, parties involved in international shipping are forced to resort to a patchwork of emails, chat transcripts, and data moved between various players' custom platforms — all tedious, complicated, and prone to errors or tampering. Morpheus.Network's integrated solution enables everyone involved in a shipment to access its official, verifiable documents — such as bills of lading, invoices, or tax documentation — not only with less friction, but also with the confidence that documents are verified as tamper-free originals. Morpheus.Network calls this a shipment's Digital Footprint: its documentation library and log of transport and import/export events, collected into a single source of truth. In an industry that's long been a holdout of old-fashioned paper tracking processes, this gives players moving to fully-digital shipment tracking an additional means for leapfrogging the competition. Says Weinberger: "There's no reason to digitize if you're not futureproofing as well."
+Without the IPFS-backed document management system that Morpheus.Network offers, parties involved in international shipping are forced to resort to a patchwork of emails, chat transcripts, and data moved between various players' custom platforms — all tedious, complicated, and prone to errors or tampering. Morpheus.Network's integrated solution enables everyone involved in a shipment to access its official, verifiable documents — such as bills of lading, invoices, or tax documentation — not only with less friction, but also with the confidence that documents are verified as tamper-free originals. Morpheus.Network calls this a shipment's Digital Footprint: its documentation library and log of transport and import/export events, collected into a single source of truth. In an industry that's long been a holdout of old-fashioned paper tracking processes, this gives players moving to fully-digital shipment tracking an additional means for leapfrogging the competition. Says Weinberger: "There's no reason to digitize if you're not future-proofing as well."
 
 ![Digital Footprint example](./images/case-studies/img-morpheus-digitalfootprint.png)