fixing crefs

Author: maddymontaquila

docs/compatibility/9.3/remove-publisher-apis.md

@@ -24,9 +24,9 @@ In .NET Aspire 9.2, the publisher API was introduced in preview, allowing the us
 
 These publishers were added using the following methods:
 
-- <xref:Aspire.Hosting.DockerComposePublisherExtensions.AddDockerComposePublisher*>
-- <xref:Aspire.Hosting.KubernetesPublisherExtensions.AddKubernetesPublisher*>
-- <xref:Aspire.Hosting.AzurePublisherExtensions.AddAzurePublisher*>
+- `Aspire.Hosting.DockerComposePublisherExtensions.AddDockerComposePublisher*`
+- `Aspire.Hosting.KubernetesPublisherExtensions.AddKubernetesPublisher*`
+- `Aspire.Hosting.AzurePublisherExtensions.AddAzurePublisher*`
 
 Multiple publishers could be added, and the `aspire publish` CLI command allowed users to select one for publishing.
 

docs/diagnostics/aspireazure001.md

@@ -14,7 +14,7 @@ helpviewer_keywords:
 
 > Publishers are for evaluation purposes only and are subject to change or removal in future updates. Suppress this diagnostic to proceed.
 
-The .NET Aspire Azure hosting integration now ships with a publisher. If you're using any of the <xref:Aspire.Hosting.AzurePublisherExtensions.AddAzurePublisher*> APIs, you might see a compiler error/warning indicating that the API is experimental. This behavior is expected, as the API is still in preview and the shape of this API is expected to change in the future.
+The .NET Aspire Azure hosting integration now ships with a publisher. If you're using any of the `Aspire.Hosting.AzurePublisherExtensions.AddAzurePublisher*` APIs, you might see a compiler error/warning indicating that the API is experimental. This behavior is expected, as the API is still in preview and the shape of this API is expected to change in the future.
 
 ## Example