Merge pull request #182 from 0xScratch/fixes

Fixed Broken links
Apillon · May 23, 2024 · 1fa7b69 · 1fa7b69
2 parents 0307b2b + cf0bc94
commit 1fa7b69
Show file tree

Hide file tree

Showing 3 changed files with 6 additions and 6 deletions.
diff --git a/build/4-nfts-api.md b/build/4-nfts-api.md
@@ -30,7 +30,7 @@ API is for creating and managing NFTs. To prepare images and metadata for your N
 | ---------------- | ---------- | ------------------------------------------------------------------------------------------------------ |
 | createTime       | `DateTime` | Collection create time.                                                                                |
 | updateTime       | `DateTime` | Collection last update time.                                                                           |
-| collectionType   | `number`   | Type of smart contract to use for collection. Available types are described [here](#collection-types). |
+| collectionType   | `number`   | Type of smart contract to use for collection. Available types are described [here](#collection-type). |
 | collectionUuid   | `string`   | Unique key of a collection.                                                                            |
 | symbol           | `string`   | NFT collection symbol (usually 3-4 characters long).                                                   |
 | name             | `string`   | NFT collection name.                                                                                   |
@@ -316,7 +316,7 @@ An NFT Collection can be created with a few features/functionalities:
 2 types of collections are supported:
 
 1. Generic collection, which represents an extension of the ERC-721 standard for EVM collections and the PSP-34 standard for substrate collections. You can read more about these standards [here](/web3-services/4-nfts.html#nft-files)
-2. Nestable collection which allows nesting NFTs under each other (based on [RMRKs ERC-7401](https://evm.rmrk.app/general-overview/rmrk-legos/nestable) NFT standard - EVM only)
+2. Nestable collection which allows nesting NFTs under each other (based on [RMRKs ERC-7401](https://evm.rmrk.app/nestable) NFT standard - EVM only)
 
 Additionally, 2 chain types/environments are supported: EVM and Substrate.
 

diff --git a/build/6-apillon-cli.md b/build/6-apillon-cli.md
@@ -66,7 +66,7 @@ For commands that return a list of results, for example `apillon storage list-fi
 - `--page <integer>`: Page number
 - `--search <string> `: Search by name or other object identifier
 
-> For example responses and for an overview of all properties, refer to [the Apillon API wiki](https://wiki.apillon.io/build/1-apillon-api.html). Note: CLI responses may be dfferent from API responses.
+> For example responses and for an overview of all properties, refer to [the Apillon API wiki](https://wiki.apillon.io/build/1-apillon-api.html). Note: CLI responses may be different from API responses.
 
 # Commands
 
@@ -782,8 +782,8 @@ jobs:
 
       ####
       ## if you are using a framework for building web app, you can replace previous two step with the
-      ## appropriate command for generating static webpage, like an example bellow.
-      ## Find the correct command in your framework documentation. You may need to to change the
+      ## appropriate command for generating static webpage, like the example below.
+      ## Find the correct command in your framework documentation. You may need to change the
       ## name of the source folder in the last step (CLI call)
       ####
 

diff --git a/build/9-social-api.md b/build/9-social-api.md
@@ -1,6 +1,6 @@
 # Social API
 
-The Social API provides endpoints to list, get and create subsocial entities used in tge [Grill widget](https://github.com/dappforce/grillchat/tree/main/integration).
+The Social API provides endpoints to list, get and create subsocial entities used in the [Grill widget](https://github.com/dappforce/grillchat/tree/main/integration).
 Spaces and posts are the main entities provided by it, which may be a bit unfamiliar to a developer who is trying to include the Grill widget into a website.
 Apillon changes the naming of these entities into **Hub** and **Channel**, and takes care of the whole blockchain and IPFS aspect, the result being a simple configuration which can be used to setup a Grill widget on any website.