diff --git a/pages/developers/eigenlayer-avs/bls-template.mdx b/pages/developers/eigenlayer-avs/bls-template.mdx
index 4901dd6..2df02a3 100644
--- a/pages/developers/eigenlayer-avs/bls-template.mdx
+++ b/pages/developers/eigenlayer-avs/bls-template.mdx
@@ -43,6 +43,7 @@ you aren't sure about a question, you likely just want the default selection tha
 #### Note
 
 If you choose to use `foundry.toml` for the Soldeer configuration (the default), you will need to delete the following files from the `contracts` directory:
+
 - `foundry.toml`
 - `remappings.txt`
 - `soldeer.lock`
@@ -64,6 +65,6 @@ This test just shows that the template generates you a fresh, working AVS struct
 What you do from here is completely up to you, but we have plenty of resources to help you:
 
 - The contracts generated with this template will be called TangleServiceManager.sol, TangleTaskManager.sol, and
-ITangleTaskManager.sol by default. You can use the find-and-replace function to change these to whatever you would like.
+  ITangleTaskManager.sol by default. You can use the find-and-replace function to change these to whatever you would like.
 - Examples of different types of event listeners can be found [here](/developers/blueprint-event-listeners/introduction).
 - A deeper dive into how jobs work can be found in the [jobs section](/developers/blueprint-macros/jobs).
diff --git a/pages/developers/eigenlayer-avs/ecdsa-template.mdx b/pages/developers/eigenlayer-avs/ecdsa-template.mdx
index a709b97..480e260 100644
--- a/pages/developers/eigenlayer-avs/ecdsa-template.mdx
+++ b/pages/developers/eigenlayer-avs/ecdsa-template.mdx
@@ -44,6 +44,7 @@ uncertain, the default selection is generally best.
 
 If you choose to use `foundry.toml` for the Soldeer configuration (the default), you will need to delete the following
 files from the `contracts` directory:
+
 - `foundry.toml`
 - `remappings.txt`
 - `soldeer.lock`
@@ -66,7 +67,7 @@ This test just shows that the template generates you a fresh, working AVS struct
 The next steps depend on your specific requirements, but we offer several resources to assist you:
 
 - By default, the AVS contract generated with this template is named TangleServiceManager.sol (along with related test
-files TestTangleServiceManager.sol and TangleServiceManager.t.sol). You can use your text editor's find-and-replace
-function to rename these as desired.
+  files TestTangleServiceManager.sol and TangleServiceManager.t.sol). You can use your text editor's find-and-replace
+  function to rename these as desired.
 - For various types of event listener examples, refer to [this page](/developers/blueprint-event-listeners/introduction).
 - To gain a deeper understanding of how jobs function, consult the [jobs section](/developers/blueprint-macros/jobs).
diff --git a/pages/developers/eigenlayer-avs/incredible-squaring-avs.mdx b/pages/developers/eigenlayer-avs/incredible-squaring-avs.mdx
index b44d702..9bbe1fd 100644
--- a/pages/developers/eigenlayer-avs/incredible-squaring-avs.mdx
+++ b/pages/developers/eigenlayer-avs/incredible-squaring-avs.mdx
@@ -118,7 +118,6 @@ Running the AVS on a Testnet
 RUST_LOG=gadget=trace cargo test --package incredible-squaring-blueprint-eigenlayer test_eigenlayer_incredible_squaring_blueprint -- --nocapture
 ```
 
-
 ## Best Practices and Considerations
 
 1. **Error Handling**: Implement robust error handling in your event listener functions to manage potential failures gracefully.
diff --git a/pages/resources/safe.mdx b/pages/resources/safe.mdx
index 467f5eb..3252ec2 100644
--- a/pages/resources/safe.mdx
+++ b/pages/resources/safe.mdx
@@ -8,9 +8,9 @@ Safe contracts deployed deployed and a [Safe UI is hosted by Den](https://safe.o
 
 Below are the key contract deployments for Safe on the Tangle network. You can view each contract on our [Blockscout Explorer](https://explorer.tangle.tools/).
 
-| Contract Name | Address                                                                                                                          |
-| ------------ | -------------------------------------------------------------------------------------------------------------------------------- |
+| Contract Name           | Address                                                                                                                          |
+| ----------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
 | **Safe Implementation** | [`0xfb1bffC9d739B8D520DaF37dF666da4C687191EA`](https://explorer.tangle.tools/address/0xfb1bffC9d739B8D520DaF37dF666da4C687191EA) |
-| **Proxy Factory** | [`0xC22834581EbC8527d974F8a1c97E1bEA4EF910BC`](https://explorer.tangle.tools/address/0xC22834581EbC8527d974F8a1c97E1bEA4EF910BC) |
+| **Proxy Factory**       | [`0xC22834581EbC8527d974F8a1c97E1bEA4EF910BC`](https://explorer.tangle.tools/address/0xC22834581EbC8527d974F8a1c97E1bEA4EF910BC) |
 
 These contract addresses are essential for interacting with Safe on Tangle. Ensure you understand the functionality and security implications when interacting with these contracts.