fixing crefs

Author: maddymontaquila

docs/whats-new/dotnet-aspire-9.4.md

@@ -109,9 +109,9 @@ The `aspire deploy` command supports extensible deployment workflows through the
 
 **Key capabilities:**
 
-- **Custom deployment hooks** using <xref:Aspire.Hosting.Publishing.DeployingCallbackAnnotation> to execute custom logic during the `aspire deploy` command
+- **Custom deployment hooks** using `Aspire.Hosting.Publishing.DeployingCallbackAnnotation` to execute custom logic during the `aspire deploy` command
 - **Workflow activity reporting** via the <xref:Aspire.Hosting.Publishing.IPublishingActivityReporter> to support progress notifications and prompting in commmands
-- **Integration with publish** - `aspire deploy` runs <xref:Aspire.Hosting.Publishing.PublishingCallbackAnnotations> to support deploying artifacts emitted by publish steps, if applicable
+- **Integration with publish** - `aspire deploy` runs `Aspire.Hosting.Publishing.PublishingCallbackAnnotations` to support deploying artifacts emitted by publish steps, if applicable
 
 The example below demonstrates using the `DeployingCallbackAnnotation` to register custom deployment behavior and showcases [CLI-based prompting](#-enhanced-publish-and-deploy-output) and progress notifications.
 
@@ -200,7 +200,7 @@ This custom deployment logic executes as follows from the `aspire deploy` comman
 Now, integration owners can create sophisticated `aspire deploy` workflows. This work also provides a foundation for advanced deployment automation scenarios.
 
 > [!NOTE]
-> While the <xref:Aspire.Hosting.Publishing.DeployingCallbackAnnotation> API is available in .NET Aspire 9.4, there are currently no built-in resources that natively support deployment callbacks. Built-in resource support for deployment callbacks will be added in the next version of .NET Aspire.
+> While the `Aspire.Hosting.Publishing.DeployingCallbackAnnotation` API is available in .NET Aspire 9.4, there are currently no built-in resources that natively support deployment callbacks. Built-in resource support for deployment callbacks will be added in the next version of .NET Aspire.
 
 > [!IMPORTANT]
 > 🧪 **Feature Flag**: The `aspire deploy` command is behind a feature flag and **disabled by default** in this release. It must be explicitly enabled for use with `aspire config set features.deployCommandEnabled true`
@@ -376,9 +376,9 @@ This feature eliminates the need to pre-configure all parameters in appsettings.
 
 Building on the interactive parameter prompting capabilities and the new [interaction service](#-interaction-service), Aspire 9.4 introduces rich parameter descriptions and custom input rendering to provide better user guidance and specialized input controls during parameter collection.
 
-- **<xref:Aspire.Hosting.ParameterResourceBuilderExtensions.WithDescription>** - Add helpful descriptions to guide users during parameter input
+- **Aspire.Hosting.ParameterResourceBuilderExtensions.WithDescription** - Add helpful descriptions to guide users during parameter input
 - **Markdown support** - Rich text descriptions with links, formatting, and lists using `enableMarkdown: true`
-- **<xref:Aspire.Hosting.ParameterResourceBuilderExtensions.WithCustomInput>** - Create specialized input controls for specific parameter types
+- **Aspire.Hosting.ParameterResourceBuilderExtensions.WithCustomInput** - Create specialized input controls for specific parameter types
 
 ```csharp
 var builder = DistributedApplication.CreateBuilder(args);
@@ -534,7 +534,7 @@ builder.Build().Run();
 
 **Enhanced capabilities:**
 
-- **Improved lifecycle coordination** between <xref:Aspire.Hosting.ResourceBuilderExtensions.WithExplicitStart> and `ContainerLifetime.Persistent`
+- **Improved lifecycle coordination** between `Aspire.Hosting.ResourceBuilderExtensions.WithExplicitStart` and `ContainerLifetime.Persistent`
 - **Automatic persistent networking** spun up when persistent containers are detected
 - **Container delay start** for more reliable startup sequencing
 - **Network isolation** between persistent and session-scoped containers, which now use separate networks for better resource management
@@ -543,7 +543,7 @@ This will greatly improve your experience while building stateful services that
 
 ### 🎛️ Resource command service
 
-.NET Aspire 9.4 introduces <xref:Aspire.Hosting.ApplicationModel.ResourceCommandService>, an API for executing commands against resources. You can now easily execute the commands that appear in the dashboard programmatically. For example, when writing unit tests for commands, or having other integrations in Aspire execute commands.
+.NET Aspire 9.4 introduces `Aspire.Hosting.ApplicationModel.ResourceCommandService`, an API for executing commands against resources. You can now easily execute the commands that appear in the dashboard programmatically. For example, when writing unit tests for commands, or having other integrations in Aspire execute commands.
 
 The example below uses `ResourceCommandService` to have a command execute other commands.
 
@@ -639,7 +639,7 @@ public async Task Should_ResetCache_WhenTestStarts()
 
 ### 🔄 Resource lifecycle events
 
-.NET Aspire 9.4 introduces convenient extension methods on <xref:Aspire.Hosting.ApplicationModel.IResourceBuilder>` that make it much easier to subscribe to [lifecycle events](../app-host/eventing.md#app-host-life-cycle-events) directly on resources, providing a cleaner and more intuitive API.
+.NET Aspire 9.4 introduces convenient extension methods on `Aspire.Hosting.ApplicationModel.IResourceBuilder` that make it much easier to subscribe to [lifecycle events](../app-host/eventing.md#app-host-life-cycle-events) directly on resources, providing a cleaner and more intuitive API.
 
 ```csharp
 var builder = DistributedApplication.CreateBuilder(args);
@@ -705,11 +705,11 @@ builder.Build().Run();
 
 **Available lifecycle events:**
 
-- <xref:Aspire.Hosting.DistributedApplicationEventingExtensions.OnInitializeResource> - Called during early resource initialization
-- <xref:Aspire.Hosting.DistributedApplicationEventingExtensions.OnBeforeResourceStarted> - Called before the resource starts
-- <xref:Aspire.Hosting.DistributedApplicationEventingExtensions.OnConnectionStringAvailable> - Called when connection strings are resolved (requires `IResourceWithConnectionString`)
-- <xref:Aspire.Hosting.DistributedApplicationEventingExtensions.OnResourceEndpointsAllocated> - Called when resource endpoints are allocated (requires `IResourceWithEndpoints`)
-- <xref:Aspire.Hosting.DistributedApplicationEventingExtensions.OnResourceReady> - Called when the resource is fully ready
+- `OnInitializeResource` - Called during early resource initialization
+- `OnBeforeResourceStarted` - Called before the resource starts
+- `OnConnectionStringAvailable` - Called when connection strings are resolved (requires `IResourceWithConnectionString`)
+- `OnResourceEndpointsAllocated` - Called when resource endpoints are allocated (requires `IResourceWithEndpoints`)
+- `OnResourceReady` - Called when the resource is fully ready
 
 The new chainable fluent API, strongly-typed callbacks, and simplified syntax make it intuitive to hook into your resource lifecycles for interactions, commands, custom scripts, and more.
 
@@ -1140,7 +1140,7 @@ All database providers now support `WithInitFiles()` method, replacing the more
 
 ### 🏷️ Consistent resource name exposure
 
-.NET Aspire 9.4 now consistently exposes the actual names of all Azure resources through the <xref:Aspire.Hosting.Azure.NameOutputReference> property. This enables applications to access the real Azure resource names that get generated during deployment, which is essential for scenarios requiring direct Azure resource coordination. This is particularly valuable for external automation scripts and monitoring and alerting systems that reference resources by their actual names.
+.NET Aspire 9.4 now consistently exposes the actual names of all Azure resources through `Aspire.Hosting.Azure.NameOutputReference` property. This enables applications to access the real Azure resource names that get generated during deployment, which is essential for scenarios requiring direct Azure resource coordination. This is particularly valuable for external automation scripts and monitoring and alerting systems that reference resources by their actual names.
 
 ### 🗄️ Azure Cosmos DB
 
@@ -1294,8 +1294,8 @@ var webApi = builder.AddProject<Projects.WebAPI>("webapi")
 
 **Key features**:
 
-- <xref.Aspire.Hosting.Azure.KeyVault.AzureKeyVaultResourceExtensions.AddSecret> method for adding new secrets to Key Vault from parameters or expressions
-- <xref.Aspire.Hosting.Azure.KeyVault.AzureKeyVaultResourceExtensions.GetSecret> method for referencing existing secrets in Key Vault
+- `Aspire.Hosting.Azure.KeyVault.AzureKeyVaultResourceExtensions.AddSecret` method for adding new secrets to Key Vault from parameters or expressions
+- `Aspire.Hosting.Azure.KeyVault.AzureKeyVaultResourceExtensions.GetSecret` method for referencing existing secrets in Key Vault
 - **Strongly-typed secret references** that can be used with `WithEnvironment()` for environment variables
 - **Custom secret naming** support with optional `secretName` parameter