diff --git a/content/terraform-docs-common/docs/docs/tools/mcp-server/prompt.mdx b/content/terraform-docs-common/docs/docs/tools/mcp-server/prompt.mdx
index b3ec9879b..9a6755462 100644
--- a/content/terraform-docs-common/docs/docs/tools/mcp-server/prompt.mdx
+++ b/content/terraform-docs-common/docs/docs/tools/mcp-server/prompt.mdx
@@ -34,8 +34,9 @@ You can use the following set of prompts as a guide to help you write your own c
 
 The following prompt runs the [`resolveProviderDocID`](/terraform/docs/tools/mcp-server#resolveproviderdocid) tool, which obtains a list of related provider document IDs so that you can decide which resources to create:
 
-> "I need help understanding what resources are available in the Google provider that are for AI"
-
+```
+I need help understanding what resources are available in the Google provider that are for AI
+```
 
 #### Response
 
@@ -104,7 +105,9 @@ The client prints the following response using the context acquired from the MCP
 
 The following prompt runs the [`resolveProviderDocID`](/terraform/docs/tools/mcp-server#resolveproviderdocid) tool, which gets a list of provider documentation IDs. Next, the [`getProviderDocs`](/terraform/docs/tools/mcp-server#getproviderdocs) tool calls the appropriate documentation for the use case:
 
-> "I need help setting up storage buckets in the azure provider"
+```
+I need help setting up storage buckets in the azure provider
+```
 
 #### Response
 
@@ -306,7 +309,9 @@ The client prints the following response using the context acquired from the MCP
 
 The following prompt runs the [`searchModules`](/terraform/docs/tools/mcp-server#searchmodules) tool, which gets a list of modules:
 
-> "Is there a module to help with setting up an IBM VM?"
+```
+Is there a module to help with setting up an IBM VM?
+```
 
 #### Response