docs: fix build issues (ApeWorX#2544)

Co-authored-by: El De-dog-lo <[email protected]>

Author: antazoey

docs/index.rst

@@ -2,37 +2,25 @@
     :plugin-prefix: ape_
     :userguides:
         - quickstart
-        
-        # Getting Started with Your Project
         - projects
         - config
         - installing_plugins
         - dependencies
-        
-        # Development Workflow
         - accounts
         - compile
         - contracts
         - testing
         - reverts
-        
-        # Deployment and Networks
         - networks
         - forking_networks
         - publishing
         - proxy
         - contract_metadata
-        
-        # Interacting with Contracts
         - console
         - scripts
         - transactions
         - trace
-        
-        # Debugging and Analysis
         - logging
         - data
-        
-        # Customization
         - clis
         - developing_plugins

docs/userguides/contracts.md

@@ -95,11 +95,13 @@ More information on publishing contracts can be found in [this guide](./publishi
 
 You can also use the [at() method](../methoddocs/contracts.html#ape.contracts.base.ContractContainer.at) from the same top-level project manager when you know the address of an already-deployed contract:
 
-````python
+```python
 from ape import project
 
 contract = project.MyContract.at("0x68b3465833fb72A70ecDF485E0e4C7bD8665Fc45")
 
+```
+
 By default, Ape will detect if the contract is a proxy and use the implementation contract's interface. See the [Proxy Contracts guide](./proxy.html) for more details on proxy handling.
 
 ## From Any Address
@@ -110,7 +112,7 @@ If you already know the address of a contract, you can create instances of it us
 from ape import Contract
 
 contract = Contract("0x68b3465833fb72A70ecDF485E0e4C7bD8665Fc45")
-````
+```
 
 If the contract ABI and/or code is cached on disk or in memory (such as from a previous deploy or retrieval), it will use it.
 Otherwise, it will fetch the `ContractType` using the explorer plugin from the active network, such as [ape-etherscan](https://github.com/ApeWorX/ape-etherscan).
@@ -192,7 +194,7 @@ def main():
 Then, after you have a contract instance, you can call methods on the contract.
 For example, let's say you have a Vyper contract containing some functions:
 
-```python
+```vyper
 wdAmount: public(uint256)
 
 @pure

docs/userguides/scripts.md

@@ -38,7 +38,7 @@ By default, `cli` scripts do not have [`ape.cli.network_option`](../methoddocs/c
 
 However, you can add the `network_option` or `ConnectedProviderCommand` to your scripts by importing them from the `ape.cli` namespace:
 
-````python
+```python
 import click
 from ape.cli import ConnectedProviderCommand
 
@@ -56,7 +56,8 @@ def cli(network, provider):
     click.echo(f"You are connected to network '{network.name}'.")
     click.echo(provider.chain_id)
 
-    
+```
+
 ## Multi-Network Commands
 
 Scripts can use the context manager for multi-network functionality.
@@ -93,7 +94,7 @@ def cli():
 
     # Back to the original network
     print(f"Back to {network1}")
-````
+```
 
 This pattern is especially useful for cross-chain operations, data gathering from multiple networks, or comparing state between networks.