Fix documentation validation errors

- Fix bookmark reference in service-bus-ip-filtering.md (#use-a-template)
- Fix duplicate tab IDs in enable-partitions-basic-standard.md (bicep-topic/arm-topic)

Author: EldertGrootenboerMS

articles/service-bus-messaging/enable-partitions-basic-standard.md

@@ -154,7 +154,7 @@ resource serviceBusNamespace 'Microsoft.ServiceBus/namespaces@2024-01-01' = {
 
 To **create a topic with partitioning enabled**, set `enablePartitioning` to `true` in the topic properties section. For more information, see [Microsoft.ServiceBus namespaces/topics template reference](/azure/templates/microsoft.servicebus/namespaces/topics?tabs=json). 
 
-# [Bicep](#tab/bicep)
+# [Bicep](#tab/bicep-topic)
 
 ```bicep
 @description('Name of the Service Bus namespace')
@@ -182,7 +182,7 @@ resource serviceBusNamespace 'Microsoft.ServiceBus/namespaces@2024-01-01' = {
 }
 ```
 
-# [ARM template](#tab/arm)
+# [ARM template](#tab/arm-topic)
 
 ```json
 {

articles/service-bus-messaging/service-bus-ip-filtering.md

@@ -22,7 +22,7 @@ Apply the IP firewall rules at the Service Bus namespace level. Therefore, the r
 > The networking options differ between Service Bus SKUs. The **Standard SKU** supports IP filtering but does not include the "Trusted Services" option. For Premium SKU networking features, please refer to the dedicated Premium SKU networking documentation.
 
 ## Important points
-- Private Endpoints and Service Endpoints are supported only in the **premium** tier of Service Bus. If upgrading to the **premium** tier isn't an option, you can use IP firewall rules by using the [Azure portal](#use-azure-portal), [Azure Resource Manager templates](#use-resource-manager-template), [Azure CLI](#use-azure-cli), [PowerShell](#use-azure-powershell), or [REST API](#rest-api).
+- Private Endpoints and Service Endpoints are supported only in the **premium** tier of Service Bus. If upgrading to the **premium** tier isn't an option, you can use IP firewall rules by using the [Azure portal](#use-azure-portal), [Azure Resource Manager templates](#use-a-template), [Azure CLI](#use-azure-cli), [PowerShell](#use-azure-powershell), or [REST API](#rest-api).
 - Specify **at least one IP firewall rule or virtual network rule** for the namespace to allow traffic only from the specified IP addresses or subnet of a virtual network. If there are no IP and virtual network rules, the namespace is accessible over the public internet (using the access key).  
 - Implementing firewall rules can prevent other Azure services from interacting with Service Bus. As an exception, you can allow access to Service Bus resources from certain **trusted services** even when IP filtering is enabled. For a list of trusted services, see [Trusted services](#trusted-microsoft-services).