Update syntax

Author: jlin27

mdx/guides/0x-v4-nft-features-over.mdx

@@ -1,8 +1,9 @@
 # 0x V4 NFT Features Overview
 
-> Note: his feature is in beta and is subject to change. Testnet deployments coming soon, mainnet deployments are pending audit.
+> Note: This feature is in beta and is subject to change. Testnet deployments coming soon. Mainnet deployments are pending audit.
+> We invite you to join our [Discord](https://discord.com/invite/YyG9fkK) and share feedback in the [#dev-feature-feedback](https://discord.com/channels/435912040142602260/936366257521954857).
 
-We are adding support for ERC721<>ERC20 and ERC1155<>ERC20 orders to 0x v4. Contracts can be found [here](https://github.com/0xProject/protocol/tree/refactor/nft-orders/contracts/zero-ex/contracts/src/features/nft_orders). Contract interfaces are also in this doc. 
+We are adding support for ERC721<>ERC20 and ERC1155<>ERC20 orders to 0x v4. Contracts can be found [here](https://github.com/0xProject/protocol/tree/refactor/nft-orders/contracts/zero-ex/contracts/src/features/nft_orders). Contract interfaces are also in [this doc](https://0x.org/docs/guides/0x-v4-nft-contract-interfaces)
 
 ## Basics
 
@@ -25,7 +26,7 @@ enum TradeDirection {
 }
 ```
 
-## Collection/floor/property-based orders
+## Collection/Floor/Property-Based Orders
 
 In lieu of specifying a particular token ID, buy orders can specify a list of properties that an NFT asset must satisfy to be used to fill the order.
 
@@ -127,7 +128,7 @@ For cheaper chains like Polygon, it may make sense for orders to specify multipl
 
 For expensive chains like Ethereum mainnet, disbursing multiple fees would be costly, so instead an order can specify a single `Fee`, the `recipient` of which is a contract that would handle splitting the fee between multiple recipients using a withdrawal model. 
 
-## ETH/WETH handling
+## ETH/WETH Handling
 
 A **sell** order must use WETH instead of ETH, since we require the ERC20 `transferFrom` functionality to transfer WETH from the maker to the taker. Even so, the taker can choose to *receive* ETH when filling a WETH sell order by setting the `unwrapNativeToken` parameter to `true` in `sellERC721` or `sellERC1155`.
 
@@ -139,7 +140,7 @@ A **buy** order can specify either ETH or WETH, i.e. the buyer can indicate whet
 
 This allows takers to fill an NFT buy order without needing to first approving the 0x contract. As a side-effect, this will also mitigate the risk of users accidentally sending NFTs to the 0x contract.
 
-## Order matching
+## Order Matching
 
 The `matchERC721Orders` function can be used to simultaneously fill a sell order and a buy order if:
 
@@ -148,7 +149,7 @@ The `matchERC721Orders` function can be used to simultaneously fill a sell order
 
 Order matching is currently only support for ERC721 orders. Support for ERC1155 order matching will be added at a future date if there is sufficient interest. 
 
-## Pre-signing orders
+## Pre-Signing Orders
 
 Since smart contracts cannot sign orders in the traditional sense, they can instead “sign” orders by calling the `preSignERC721Order` or `preSignERC1155Order` functions.
 
@@ -167,4 +168,4 @@ A smart contract can subsequently cancel an order just like an EOA would, by cal
 
 The pre-sign functions will emit the entire order as an event, so that the order is easily indexable by subgraphs and thus easily discoverable without the need for an off-chain database. 
 
-Note that EOAs can also call the pre-sign functions if they so desire.
+Note that EOAs can also call the pre-sign functions if they so desire.