Address build issues

.openpublishing.redirection.json

@@ -251,6 +251,14 @@
     {
       "source_path_from_root": "/docs/storage/azure-storage-tables-component.md",
       "redirect_url": "/dotnet/aspire/storage/azure-storage-tables-integration"
+    },
+    {
+      "source_path_from_root": "/docs/extensibility/custom-resources.md",
+      "redirect_url": "/dotnet/aspire/extensibility/custom-hosting-integration"
+    },
+    {
+      "source_path_from_root": "/docs/extensibility/custom-integration.md",
+      "redirect_url": "/dotnet/aspire/extensibility/custom-client-integration"
     }
   ]
 }

docs/extensibility/custom-hosting-integration.md

@@ -267,7 +267,7 @@ To use the SMTP connection details that were injected into the newsletter servic
 :::code source="snippets/MailDevResource/MailDevResource.NewsletterService/Program.cs" id="smtp":::
 
 > [!TIP]
-> This code snippet relies on the official `SmtpClient`, however; this type is obsolete on some platforms and not recommended on others. This is used here to demonstrate a non-componentized approach to using the MailDev resource. For a more modern approach using [MailKit](https://github.com/jstedfast/MailKit), see [Create custom .NET Aspire integration](custom-integration.md).
+> This code snippet relies on the official `SmtpClient`, however; this type is obsolete on some platforms and not recommended on others. For a more modern approach using [MailKit](https://github.com/jstedfast/MailKit), see [Create custom .NET Aspire client integration](custom-client-integration.md).
 
 To test the client, add two simple `subscribe` and `unsubscribe` POST methods to the newsletter service. Add the following code replacing the "weatherforecast" `MapGet` call in the _:::no-loc text="Program.cs":::_ file of the _MailDevResource.NewsletterService_ project to set up the ASP.NET Core routes:
 

docs/extensibility/implement-auth-from-resource-to-integration.md

@@ -7,10 +7,7 @@ ms.topic: how-to
 
 # Implement auth for hosting and client integrations
 
-This article is a continuation of two previous articles:
-
-- [Create custom resource types for .NET Aspire](custom-resources.md)
-- [Create custom .NET Aspire integration](custom-integration.md)
+This article is a continuation of two previous articles demonstrating the creation of [custom hosting integrations](custom-hosting-integration.md) and [custom client integrations](custom-client-integration.md).
 
 One of the primary benefits to .NET Aspire is how it simplifies the configurability of resources and consuming clients (or integrations). This article demonstrates how to authentication credentials from a custom resource to a custom integration. The custom resource is a MailDev container that allows for either incoming or outgoing credentials. The custom integration is a MailKit client that sends emails.
 

docs/fundamentals/integrations-overview.md

@@ -20,13 +20,13 @@ There are two types of integrations in .NET Aspire, each with a different respon
 
 Hosting integrations configure applications by provisioning resources (like containers or cloud resources) or pointing to existing ones (such as a local SQL server). These packages model various services, platforms, or capabilities, including caches, databases, logging, storage, and messaging systems. They extend the <xref:Aspire.Hosting.IDistributedApplicationBuilder> interface, enabling the _app host_ project to express resources within its _app model_. The official [hosting integration NuGet packages](https://www.nuget.org/packages?q=owner%3A+aspire+tags%3A+aspire+hosting+integration&includeComputedFrameworks=true&prerel=true&sortby=relevance) are tagged with `aspire`, `integration`, and `hosting`.
 
-For information on creating a custom hosting integration, see [Create a custom hosting integration](../extensibility/custom-resources.md).
+For information on creating a custom hosting integration, see [Create custom .NET Aspire hosting integration](../extensibility/custom-hosting-integration.md).
 
 ### Client integrations
 
 Client integrations define configuration schema, wire up client libraries to dependency injection (DI), add health checks, resiliency, and telemetry where applicable. These packages configure existing libraries to connect to resource-backed integrations. They extend the <xref:Microsoft.Extensions.DependencyInjection.IServiceCollection> interface allowing client-consuming projects to use the connected resource. The official [client integration NuGet packages](https://www.nuget.org/packages?q=owner%3A+aspire+tags%3A+aspire+client+integration&includeComputedFrameworks=true&prerel=true&sortby=relevance) are tagged with `aspire`, `integration`, and `client`.
 
-For more information on creating a custom client integration, see [Create a custom client integration](../extensibility/custom-integration.md).
+For more information on creating a custom client integration, see [Create custom .NET Aspire client integration](../extensibility/custom-client-integration.md).
 
 ### Hosting and client integration relationship