Fixes build issues

Author: ggailey777

Diff for: articles/azure-functions/create-first-function-cli-python.md

@@ -304,7 +304,7 @@ In the previous example, replace `<FUNCTION_APP_NAME>` and `<RESOURCE_GROUP_NAME
 
 ## Verify in Azure
 
-Run the following command to view near real-time [streaming logs](functions-run-local.md#enable-streaming-logs) in Application Insights in the Azure portal.
+Run the following command to view near real-time streaming logs in Application Insights in the Azure portal.
 
 ```console
 func azure functionapp logstream <APP_NAME> --browser

Diff for: articles/azure-functions/functions-app-settings.md

@@ -507,7 +507,7 @@ Controls the timeout, in seconds, when connected to streaming logs. The default
 |-|-|
 |SCM_LOGSTREAM_TIMEOUT|`1800`|
 
-The above sample value of `1800` sets a timeout of 30 minutes. To learn more, see [Enable streaming logs](functions-run-local.md#enable-streaming-logs).
+The above sample value of `1800` sets a timeout of 30 minutes. For more information, see [Enable streaming execution logs in Azure Functions](streaming-logs.md).
 
 ## WEBSITE\_CONTENTAZUREFILECONNECTIONSTRING
 

Diff for: articles/azure-functions/functions-core-tools-reference.md

@@ -206,7 +206,7 @@ The `deploy` action supports the following options:
 | ------------ | -------------------------------------- |
 | **`--browser`** | Open Azure Application Insights Live Stream for the function app in the default browser. |
 
-To learn more, see [Enable streaming logs](functions-run-local.md#enable-streaming-logs).
+For more information, see [Enable streaming execution logs in Azure Functions](streaming-logs.md).
 
 ## func azure functionapp publish 
 

Diff for: articles/azure-functions/functions-run-local.md

@@ -246,18 +246,18 @@ Keep in mind the following considerations when running your functions locally:
 
 + While there's local storage emulation available, it's often best to validate your triggers and bindings against live services in Azure. You can maintain the connections to these services in the local.settings.json project file. For more information, see [Local settings file](functions-develop-local.md#local-settings-file). Make sure to keep test and production data separate when testing against live Azure services. 
 
-+ You can trigger non-HTTP functions locally without connecting to a live service. For more information, see [Non-HTTP triggered functions](#non-http-triggered-functions).
++ You can trigger non-HTTP functions locally without connecting to a live service. For more information, see [Pass data to local functions](./functions-run-local?tabs=non-http-trigger#pass-data-to-local-functions).
 
 + When you include your Application Insights connection information in the local.settings.json file, local log data is written to the specific Application Insights instance. To keep local telemetry data separate from production data, consider using a separate Application Insights instance for development and testing.
 
 ## Pass data to local functions
 
-To test your functions locally, you [start the Functions host](#start) and call endpoints on the local server using HTTP requests. The endpoint you call depends on the type of function.
+To test your functions locally, you [start the Functions host](#start) and call endpoints on the local server using HTTP requests. The endpoint you call depends on your type of function trigger.
 
->[!NOTE]
+> [!NOTE]  
 > Examples in this topic use the cURL tool to send HTTP requests from the terminal or a command prompt. You can use a tool of your choice to send HTTP requests to the local server. The cURL tool is available by default on Linux-based systems and Windows 10 build 17063 and later. On older Windows, you must first download and install the [cURL tool](https://curl.haxx.se/).
 
-### [HTTP triggers](#tab/http-trigger)
+### [HTTP trigger](#tab/http-trigger)
 
 You call this endpoint to start an HTTP triggered function:
 
@@ -327,10 +327,12 @@ The following considerations apply when using the administrator endpoint for loc
 
 + Access keys are valuable shared secrets. When used locally, they must be securely stored outside of source control. Because authentication and authorization aren't required by Functions when running locally, you should avoid using and storing access keys unless your scenarios require it.
 
-+ Event Grid triggers have other requirements for local testing. For more information, see [Local testing with viewer web app](event-grid-how-tos.md#local-testing-with-viewer-web-app).
-
 + Calling an administrator endpoint and passing test data is similar to using the **Test** tab in the Azure portal.
 
+### [Event Grid trigger](#tab/non-http-trigger)
+
+Event Grid triggers have spcific requirements to enable local testing. For more information, see [Local testing with viewer web app](event-grid-how-tos.md#local-testing-with-viewer-web-app).
+
 ---
 
 ## <a name="publish"></a>Publish to Azure

Diff for: articles/azure-functions/functions-triggers-bindings.md

@@ -4,7 +4,7 @@ description: Learn to use triggers and bindings to connect your Azure Function t
 ms.topic: conceptual
 ms.date: 08/14/2023
 ms.custom: devdivchpfy22, ignite-2022
-zone_pivot_groups: programming-languages-set-functions-lang-workers
+zone_pivot_groups: programming-languages-set-functions
 ---
 
 # Azure Functions triggers and bindings concepts

Diff for: includes/functions-streaming-logs-cli-qs.md

@@ -6,7 +6,7 @@ ms.date: 10/18/2020
 ms.author: glenga
 ---
 
-Run the following command to view near real-time [streaming logs](../articles/azure-functions/functions-run-local.md#enable-streaming-logs):
+Run the following command to view near real-time streaming logs:
 
 ```console
 func azure functionapp logstream <APP_NAME>