Update docs/toolhive/guides-k8s/tool-config.mdx

Co-authored-by: Dan Barr <[email protected]>

Author: JAORMX

docs/toolhive/guides-k8s/tool-config.mdx

@@ -89,11 +89,19 @@ The key in the `toolsOverride` map is the original tool name; the `name` field
 is the user-visible (overridden) name.
 
 :::info[Override fields]
-You can override name or description independently. Leave one unset to keep the original value from the MCP server. Both fields cannot be empty at the same time.
+
+You can override name or description independently. Leave one unset to keep the
+original value from the MCP server. Both fields cannot be empty at the same
+time.
+
 :::
 
 :::tip[When to rename?]
-If you run the same server for different scopes (for example, prod vs. sandbox), use distinct tool names like `github_prod_create_pr` and `github_sandbox_create_pr` to make intent clear to clients.
+
+If you run the same server for different scopes (for example, prod vs. sandbox),
+use distinct tool names like `github_prod_create_pr` and
+`github_sandbox_create_pr` to make intent clear to clients.
+
 :::
 
 ## Reference the configuration from an MCP server