refix links

Author: ggailey777

articles/azure-functions/durable/durable-functions-isolated-create-first-csharp.md

@@ -113,7 +113,7 @@ Azure Functions Core Tools gives you the capability to run an Azure Functions pr
 
 1. Use one of these HTTP test tools to send an HTTP POST request to the URL endpoint:
 
-   [!INCLUDE [api-test-http-request-tools](../../../../includes/api-test-http-request-tools.md)]
+   [!INCLUDE [api-test-http-request-tools](../../../includes/api-test-http-request-tools.md)]
 
    The response is the HTTP function's initial result. It lets you know that the Durable Functions app orchestration started successfully. It doesn't yet display the end result of the orchestration. The response includes a few useful URLs.
 

articles/azure-functions/event-grid-how-tos.md

@@ -129,7 +129,7 @@ To test an Event Grid trigger locally, you have to get Event Grid HTTP requests
 
 To send an HTTP post request, you need an HTTP test tool, like one of these:
 
-[!INCLUDE [api-test-http-request-tools](../../../includes/api-test-http-request-tools.md)]
+[!INCLUDE [api-test-http-request-tools](../../includes/api-test-http-request-tools.md)]
 
 When you're done testing, you can use the same subscription for production by updating the endpoint. Use the [`az eventgrid event-subscription update`](/cli/azure/eventgrid/event-subscription#az-eventgrid-event-subscription-update) Azure CLI command.
 

articles/azure-functions/functions-create-serverless-api.md

@@ -65,7 +65,7 @@ Next, test your function to see how it works with the new API surface:
 
 1. You can also call the endpoint with another HTTP method to confirm that the function isn't executed. To do so, use one of these HTTP test tools:
 
-[!INCLUDE [api-test-http-request-tools](../../../includes/api-test-http-request-tools.md)]
+[!INCLUDE [api-test-http-request-tools](../../includes/api-test-http-request-tools.md)]
 
 ## Proxies overview
 

articles/azure-functions/functions-custom-handlers.md

@@ -567,7 +567,7 @@ In Azure, [query Application Insights traces](analyze-telemetry-data.md#query-te
 
 Custom handler apps are a web server process, so it may be helpful to start it on its own and test function invocations by sending mock [HTTP requests](#request-payload) using one of these tools:
 
-[!INCLUDE [api-test-http-request-tools](../../../includes/api-test-http-request-tools.md)]
+[!INCLUDE [api-test-http-request-tools](../../includes/api-test-http-request-tools.md)]
 
 You can also use this strategy in your CI/CD pipelines to run automated tests on your custom handler.
 

articles/azure-functions/functions-manually-run-non-http.md

@@ -17,7 +17,7 @@ The procedure described in this article is equivalent to using the **Test/Run**
 
 The examples in this article use an HTTP test tool. You can obtain and use any of these tools that send HTTP requests:
 
-[!INCLUDE [api-test-http-request-tools](../../../includes/api-test-http-request-tools.md)]
+[!INCLUDE [api-test-http-request-tools](../../includes/api-test-http-request-tools.md)]
 
 ## Define the request location
 

articles/azure-functions/functions-run-local.md

@@ -276,7 +276,7 @@ The following considerations apply when calling HTTP endpoints locally:
 
 + You can make GET requests from a browser passing data in the query string. For all other HTTP methods, you must use an HTTP testing tool that supports POST requests, like one of these: 
 
-   [!INCLUDE [api-test-http-request-tools](../../../includes/api-test-http-request-tools.md)]
+   [!INCLUDE [api-test-http-request-tools](../../includes/api-test-http-request-tools.md)]
 
 + Make sure to use the same server name and port that the Functions host is listening on. You see an endpoint like this in the output generated when starting the Function host. You can call this URL using any HTTP method supported by the trigger.