diff --git a/docs/concepts/comparisons.md b/docs/concepts/comparisons.md
index 3a7dbeb7b..83a5aa378 100644
--- a/docs/concepts/comparisons.md
+++ b/docs/concepts/comparisons.md
@@ -41,7 +41,7 @@ All of these solutions use content-based addressing.
 
 | technology            | storage mechanism         | data model            | consensus mechanism         | networking stack | identifier          | address composition | use cases                | similarity to IPFS |
 | --------------------- | ------------------------- | --------------------- | --------------------------- | ---------------- | ------------------- | ------------------- | ------------------------ | ------------------ |
-| [filecoin](https://filecoin.io/docs)              | blockchain-based storage  | merkle DAG                 | proof-of-replication         | libp2p           | cid                 | cid                 | decentralized data storage | high                |
+| [filecoin](https://docs.filecoin.io/)              | blockchain-based storage  | merkle DAG                 | proof-of-replication         | libp2p           | cid                 | cid                 | decentralized data storage | high                |
 | [storj](https://storj.io/docs/)                 | decentralized storage     | erasure coding             | proof-of-retrievability       | UDP              | farmer ID           | farmer ID + file metadata | encrypted cloud storage  | medium              |
 | [Holo](https://developer.holochain.org/docs/)             | decentralized application | distributed hash table     | distributed hash table         | actor model             | agent ID            | agent ID            | decentralized applications | medium              |
 | [Swarm](https://swarm-guide.readthedocs.io/)                 | decentralized storage     | distributed hash table     | proof-of-custody              | libp2p           | chunk ID            | chunk ID            | decentralized data storage    | high       |
diff --git a/docs/how-to/work-with-pinning-services.md b/docs/how-to/work-with-pinning-services.md
index 5fb7263a1..5212e12bc 100644
--- a/docs/how-to/work-with-pinning-services.md
+++ b/docs/how-to/work-with-pinning-services.md
@@ -86,7 +86,7 @@ To add a new pinning service to IPFS Desktop or Web UI:
 
     - A **nickname** for this service. This can be helpful if, for example, you want to add two accounts from the same service.
     - Your service's **API endpoint URL**. This field only appears if you've selected a custom pinning service.
-    - You **secret access token**, provided to you by the pinning service. See the your specific pinning service documentation for more info.
+    - You **secret access token**, provided to you by the pinning service. See your specific pinning service documentation for more info.
 
     Example using Pinata and [pinata.cloud/keys](https://app.pinata.cloud/keys):
     ![Pinata secret access token](./images/work-with-pinning-services/add-service-pinata-token.jpg)
@@ -190,5 +190,5 @@ Once you're ready to open the doors to the public, create a pull request against
 
 ## Other options
 
-Pinning services that implement the the vendor-agnostic [IPFS Pinning Service API](https://ipfs.github.io/pinning-services-api-spec/) specification are supported directly in IPFS Kubo itself. To learn more, run the `ipfs pin remote --help` command.
+Pinning services that implement the vendor-agnostic [IPFS Pinning Service API](https://ipfs.github.io/pinning-services-api-spec/) specification are supported directly in IPFS Kubo itself. To learn more, run the `ipfs pin remote --help` command.