diff --git a/docs.json b/docs.json
index 1742d407..54a11d15 100644
--- a/docs.json
+++ b/docs.json
@@ -29,7 +29,12 @@
   },
   "favicon": "/favicon.png",
   "api": {
-    "baseUrl": "https://mainnet.mirrornode.hedera.com"
+    "baseUrl": "https://mainnet.mirrornode.hedera.com",
+    "openapi": [
+      "openapi.yaml",
+      "hedera-status-api.yaml",
+      "smart-contract-verification-api.yaml"
+    ]
   },
   "appearance": {
     "default": "light"
@@ -38,12 +43,13 @@
     "options": [
       "copy",
       "view",
-      "chatgpt",
+      "vscode",
       "claude",
+      "chatgpt",
       "perplexity",
       "mcp",
       "cursor",
-      "vscode"
+      "download-spec"
     ]
   },
   "markdown": {
diff --git a/evm/differences/native-devs/ed25519-integration.mdx b/evm/differences/native-devs/ed25519-integration.mdx
index 217cc191..b0b42482 100644
--- a/evm/differences/native-devs/ed25519-integration.mdx
+++ b/evm/differences/native-devs/ed25519-integration.mdx
@@ -46,7 +46,7 @@ function verifyED25519Signature(
     bytes32 messageHash,
     bytes memory signatureBlob
 ) public returns (bool) {
-    (bool success, ) = address(0x167).call(
+    (bool success, ) = address(0x16a).call(
         abi.encodeWithSignature(
             "isAuthorizedRaw(address,bytes32,bytes)",
             accountAlias,
@@ -77,7 +77,7 @@ This example demonstrates requiring multiple valid signatures for critical contr
 
 ```solidity
 function validateMultiSig(address accountAlias, bytes memory proposalData, bytes memory signatureBlob) public returns (bool) {
-    (bool success, ) = address(0x167).call(
+    (bool success, ) = address(0x16a).call(
         abi.encodeWithSignature("isAuthorized(address,bytes,bytes)", accountAlias, proposalData, signatureBlob)
     );
     return success;
diff --git a/evm/tokens/erc721.mdx b/evm/tokens/erc721.mdx
index 9514e7e2..2f4f45a6 100644
--- a/evm/tokens/erc721.mdx
+++ b/evm/tokens/erc721.mdx
@@ -7,7 +7,7 @@ description: "Use the ERC-721 non-fungible token standard on Hedera, including s
 The [ERC-721](https://ethereum.org/en/developers/docs/standards/tokens/erc-721/) standard introduces a [non-fungible token (NFT)](/support/glossary#non-fungible-token-nft) in which each issued token is unique and distinct from others. This standard defines functions and events that enable the creation, ownership, and transfer of non-fungible assets.
 
 <Info>
-**Note**:`ERC-721` Token addresses refer to full Hedera Token Service (HTS) fungible token entities. These tokens can be fully managed by HTS API calls. Additionally, by utilizing [`IERC721`](https://docs.openzeppelin.com/contracts/2.x/api/token/erc721#IERC721) interfaces or system contract functions, these tokens can also be managed by smart contracts on Hedera.
+**Note**:`ERC-721` Token addresses refer to full Hedera Token Service (HTS) non-fungible token (NFT) entities. These tokens can be fully managed by HTS API calls. Additionally, by utilizing [`IERC721`](https://docs.openzeppelin.com/contracts/2.x/api/token/erc721#IERC721) interfaces or system contract functions, these tokens can also be managed by smart contracts on Hedera.
 </Info>
 
 ## Supported Functions
diff --git a/evm/tutorials/advanced/erc721-foundry/part1-mint-burn.mdx b/evm/tutorials/advanced/erc721-foundry/part1-mint-burn.mdx
index 7cfc9830..bda07354 100644
--- a/evm/tutorials/advanced/erc721-foundry/part1-mint-burn.mdx
+++ b/evm/tutorials/advanced/erc721-foundry/part1-mint-burn.mdx
@@ -55,7 +55,7 @@ This creates a new directory with a standard Foundry project structure, includin
 
 #### Install Dependencies
 
-Foundry uses git submodules to manage dependencies. We'll install the OpenZeppelin Contracts library, which provides a standard and secure implementation of the ERC20 token.
+Foundry uses git submodules to manage dependencies. We'll install the OpenZeppelin Contracts library, which provides a standard and secure implementation of the ERC-721 token.
 
 ```bash
 forge install OpenZeppelin/openzeppelin-contracts
diff --git a/native/files/errors.mdx b/native/files/errors.mdx
index 3a7cefcb..2bc07bdd 100644
--- a/native/files/errors.mdx
+++ b/native/files/errors.mdx
@@ -9,7 +9,7 @@ Network response messages and their descriptions.
 | Network Response                        | Description                                                              |
 | --------------------------------------- | ------------------------------------------------------------------------ |
 | `FEE_SCHEDULE_FILE_PART_UPLOADED`       | Fee Schedule Proto File Part uploaded                                    |
-| `FILE_CONTENT_EMPT`                     | The contents of file are provided as empty.                              |
+| `FILE_CONTENT_EMPTY`                    | The contents of file are provided as empty.                              |
 | `FILE_DELETED`                          | the file has been marked as deleted                                      |
 | `FILE_SYSTEM_EXCEPTION`                 | Unexpected exception thrown by file system functions                     |
 | `FILE_UPLOADED_PROTO_INVALID`           | Fee Schedule Proto uploaded but not valid (append or update is required) |