fix spacing

Author: craigshoemaker

articles/sre-agent/tools.md

@@ -367,6 +367,6 @@ The following table provides a comprehensive list of all tools available to Azur
 | ValidateQuotaRequest | validate quota request <br><br>This function evaluates a quota request based on specified parameters, including quota type, region, target limit, and subscription id. <br><br>This operation determines whether the quota request adheres to approval rules and returns a validation result. <br><br>Output: <br><br>1. ApprovalResult: The status of the quota request, which can be one of the following: <br><br> - Approved: The request has been successfully approved. <br><br> - Rejected: The request has been denied. <br><br> - Pending: Additional manual approval is required. <br><br> - NotStarted: The request is incomplete and requires more details. <br><br>2. OfferType: The offer type of the subscription. <br><br>3. Reason: Provides an explanation for the validation decision. <br><br> <br><br>This function helps ensure quota requests comply with predefined rules and provides a clear decision with supporting context. |
 | VerifyExternalRegistry | Verify connectivity to an external container registry. This is useful for checking if the Container App can pull images from the specified registry. |
 | VisualizeAKSMicroserviceTopology | PREFERRED FUNCTION FOR AKS/KUBERNETES VISUALIZATIONS. Generates a detailed visual representation of microservice architectures deployed in Azure Kubernetes Service (AKS). ALWAYS USE THIS FUNCTION INSTEAD OF VisualizeApplicationComponents when working with: AKS clusters, Kubernetes, K8s, microservices in Kubernetes, pods, deployments, or Kubernetes namespaces. This specialized function provides Kubernetes-aware visualization showing relationships between deployments, pods, services and other Kubernetes resources. This is the correct choice for any request to visualize, show, map or diagram: 1) Kubernetes application architecture, 2) Help users understand the architecture of microservice connections within AKS visually, 3) Debug and troubleshoot microservice issues, or Returns a base64-encoded diagram specifically optimized for Kubernetes resource relationships. |
-| VisualizeApplicationComponents | Creates an interactive visual diagram showing how Azure resources are connected. Use this to: 1) Show the topology/relationships between resources, 2) Help users understand the architecture visually, 3) Debug connectivity issues, or 4) Present a complete picture of the applications infrastructure. The output includes nodes (resources) and edges (relationships). Use instead of GetApplicationComponentsSummary when users ask to show, visualize, draw, or diagram the connections. Returns the graph as a base64-encoded string. Input: Azure Resource Id of the application resource to visualize.Examples of usage: Visualize `<WebAppName>` in my subscription.**Keywords: Visualize, Azure Resource, Topology.** |
+| VisualizeApplicationComponents | Creates an interactive visual diagram showing how Azure resources are connected. Use this to: 1) Show the topology/relationships between resources, 2) Help users understand the architecture visually, 3) Debug connectivity issues, or 4) Present a complete picture of the applications infrastructure. The output includes nodes (resources) and edges (relationships). Use instead of GetApplicationComponentsSummary when users ask to show, visualize, draw, or diagram the connections. Returns the graph as a base64-encoded string. Input: Azure Resource Id of the application resource to visualize.Examples of usage: Visualize `<WebAppName>` in my subscription. **Keywords: Visualize, Azure Resource, Topology.** |
 | WaitInMilliSeconds | This function forces a delay for the application to trigger a wait |
 | WasAgentHelpfulInDebuggingIssue |  Submit feedback regarding the agents assistance in debugging the issue. <br><br> clearly give both choices was agent helpful? and is resolution accurate or close? <br><br> Input parameters: <br><br> - IncidentId: The unique identifier of the incident. <br><br> - wasHelpful: Indicates whether the agent was helpful in debugging the issue (true/false). Use null to skip this feedback. <br><br> - isResolutionCorrect: Indicates whether the resolution provided by the agent was accurate (true/false). Use null to skip this feedback. |