Fix build warnings

IEvangelist · IEvangelist · commit c7f56560d6a2 · 2024-10-23T13:14:40.000-05:00
diff --git a/docs/core/extensions/dependency-injection-basics.md b/docs/core/extensions/dependency-injection-basics.md
@@ -3,7 +3,7 @@ title: Dependency injection basics
 description: Learn how to use dependency injection (DI) in your .NET apps with this simple example. Follow along with this pragmatic guide to understand DI basics in C#.
 author: IEvangelist
 ms.author: dapine
-ms.date: 07/30/2024
+ms.date: 10/23/2024
 no-loc: [Transient, Scoped, Singleton, Example]
 ---
 
@@ -28,7 +28,7 @@ You need to add the package reference to the [Microsoft.Extensions.DependencyInj
 
 ## Dependency injection basics
 
-Dependency injection is a design pattern that allows you to remove hard-coded dependencies and make your application more maintainable and testable. DI is a technique for achieving [Inversion of Control (IoC)](../../architecture/modern-web-apps-azure/architectural-principles.md#dependency-inversion) between classes and their dependencies.
+Dependency injection is a design pattern that allows you to remove hard-coded dependencies and make your application more maintainable and testable. DI is a technique for achieving _Inversion of Control (IoC)_ between classes and their dependencies.
 
 The abstractions for DI in .NET are defined in the [Microsoft.Extensions.DependencyInjection.Abstractions](https://www.nuget.org/packages/Microsoft.Extensions.DependencyInjection.Abstractions) NuGet package:
 
diff --git a/docs/core/extensions/dependency-injection.md b/docs/core/extensions/dependency-injection.md
@@ -3,13 +3,13 @@ title: Dependency injection
 description: Learn how to use dependency injection within your .NET apps. Discover how to registration services, define service lifetimes, and express dependencies in C#.
 author: IEvangelist
 ms.author: dapine
-ms.date: 07/18/2024
+ms.date: 10/23/2024
 ms.topic: overview
 ---
 
 # .NET dependency injection
 
-.NET supports the dependency injection (DI) software design pattern, which is a technique for achieving [Inversion of Control (IoC)](../../architecture/modern-web-apps-azure/architectural-principles.md#dependency-inversion) between classes and their dependencies. Dependency injection in .NET is a built-in part of the framework, along with configuration, logging, and the options pattern.
+.NET supports the dependency injection (DI) software design pattern, which is a technique for achieving [Inversion of Control (IoC)](https://dotnet.microsoft.com/en-us/download/e-book/aspnet/pdf) between classes and their dependencies. Dependency injection in .NET is a built-in part of the framework, along with configuration, logging, and the options pattern.
 
 A *dependency* is an object that another object depends on. Examine the following `MessageWriter` class with a `Write` method that other classes depend on:
 
@@ -451,6 +451,5 @@ public class ExampleService
 - [Dependency injection guidelines](dependency-injection-guidelines.md)
 - [Dependency injection in ASP.NET Core](/aspnet/core/fundamentals/dependency-injection)
 - [NDC Conference Patterns for DI app development](https://www.youtube.com/watch?v=x-C-CNBVTaY)
-- [Explicit dependencies principle](../../architecture/modern-web-apps-azure/architectural-principles.md#explicit-dependencies)
 - [Inversion of control containers and the dependency injection pattern (Martin Fowler)](https://www.martinfowler.com/articles/injection.html)
 - DI bugs should be created in the [github.com/dotnet/extensions](https://github.com/dotnet/extensions/issues) repo
diff --git a/docs/core/extensions/http-ratelimiter.md b/docs/core/extensions/http-ratelimiter.md
@@ -3,7 +3,7 @@ title: Rate limiting an HTTP handler in .NET
 description: Learn how to create a client-side HTTP handler that limits the number of requests, with the inbuilt rate limiter API from .NET.
 author: IEvangelist
 ms.author: dapine
-ms.date: 03/13/2023
+ms.date: 10/23/2024
 ---
 
 # Rate limit an HTTP handler in .NET
@@ -177,4 +177,4 @@ In this article, you learned how to implement a custom `ClientSideRateLimitedHan
 - [Announcing Rate Limiting for .NET](https://devblogs.microsoft.com/dotnet/announcing-rate-limiting-for-dotnet)
 - [Rate limiting middleware in ASP.NET Core](/aspnet/core/performance/rate-limit)
 - [Azure Architecture: Rate limiting pattern](/azure/architecture/patterns/rate-limiting-pattern)
-- [Automatic retry logic in .NET](../../architecture/microservices/implement-resilient-applications/implement-http-call-retries-exponential-backoff-polly.md)
+- [Automatic retry logic in .NET](https://dotnet.microsoft.com/download/e-book/microservices-architecture/pdf)
diff --git a/docs/core/extensions/httpclient-factory.md b/docs/core/extensions/httpclient-factory.md
@@ -3,7 +3,7 @@ title: Use the IHttpClientFactory
 description: Learn how to use the HttpClient and IHttpClientFactory implementations with dependency injection in your .NET workloads.
 author: IEvangelist
 ms.author: dapine
-ms.date: 08/13/2024
+ms.date: 10/23/2024
 ---
 
 # IHttpClientFactory with .NET
@@ -303,11 +303,11 @@ For more information, see the [full example](https://github.com/dotnet/docs/tree
 - <xref:System.Net.Http.IHttpMessageHandlerFactory>
 - <xref:System.Net.Http.HttpClient>
 - [Make HTTP requests with the HttpClient][httpclient]
-- [Implement HTTP retry with exponential backoff][http-retry]
+- [Build resilient HTTP apps: Key development patterns][http-retry]
 
 [hcf-issues]: httpclient-factory-troubleshooting.md
 [di]: dependency-injection.md
 [logging]: logging.md
 [config]: configuration.md
 [httpclient]: ../../fundamentals/networking/http/httpclient.md
-[http-retry]: ../../architecture/microservices/implement-resilient-applications/implement-http-call-retries-exponential-backoff-polly.md
+[http-retry]: ../resilience/http-resilience.md
diff --git a/docs/core/extensions/options.md b/docs/core/extensions/options.md
@@ -3,15 +3,15 @@ title: Options pattern
 author: IEvangelist
 description: Learn the options pattern to represent groups of related settings in .NET apps. The options pattern uses classes to provide strongly-typed access to settings.
 ms.author: dapine
-ms.date: 08/13/2024
+ms.date: 10/23/2024
 ---
 
 # Options pattern in .NET
 
 The options pattern uses classes to provide strongly-typed access to groups of related settings. When [configuration settings](configuration.md) are isolated by scenario into separate classes, the app adheres to two important software engineering principles:
 
-- The [Interface Segregation Principle (ISP) or Encapsulation](../../architecture/modern-web-apps-azure/architectural-principles.md#encapsulation): Scenarios (classes) that depend on configuration settings depend only on the configuration settings that they use.
-- [Separation of Concerns](../../architecture/modern-web-apps-azure/architectural-principles.md#separation-of-concerns): Settings for different parts of the app aren't dependent or coupled with one another.
+- The _Interface Segregation Principle (ISP) or Encapsulation_: Scenarios (classes) that depend on configuration settings depend only on the configuration settings that they use.
+- _Separation of Concerns_: Settings for different parts of the app aren't dependent or coupled with one another.
 
 Options also provide a mechanism to validate configuration data. For more information, see the [Options validation](#options-validation) section.
 
diff --git a/docs/core/whats-new/dotnet-core-2-0.md b/docs/core/whats-new/dotnet-core-2-0.md
@@ -148,8 +148,8 @@ You can now install the .NET Core SDK independently of Visual Studio. This makes
 
 [.NET Application Architecture](https://dotnet.microsoft.com/learn/dotnet/architecture-guides) gives you access to a set of e-books that provide guidance, best practices, and sample applications when using .NET to build:
 
-- [Microservices and Docker containers](../../architecture/microservices/index.md)
-- [Web applications with ASP.NET](../../architecture/modern-web-apps-azure/index.md)
+- [Microservices and Docker containers](https://dotnet.microsoft.com/download/e-book/microservices-architecture/pdf)
+- [Web applications with ASP.NET](https://dotnet.microsoft.com/en-us/download/e-book/aspnet/pdf)
 - [Mobile applications with Xamarin](/xamarin/xamarin-forms/enterprise-application-patterns/index)
 - [Applications that are deployed to the Cloud with Azure](/azure/architecture/reference-architectures/index)
 
diff --git a/docs/fundamentals/networking/http/httpclient-guidelines.md b/docs/fundamentals/networking/http/httpclient-guidelines.md
@@ -3,7 +3,7 @@ title: HttpClient guidelines for .NET
 description: Learn about using HttpClient instances to send HTTP requests and how you can manage clients using IHttpClientFactory in your .NET apps.
 author: gewarren
 ms.author: gewarren
-ms.date: 03/08/2024
+ms.date: 10/23/2024
 ---
 
 # Guidelines for using HttpClient
@@ -101,4 +101,4 @@ The preceding code:
 - [HTTP support in .NET](http-overview.md)
 - [HTTP client factory with .NET](../../../core/extensions/httpclient-factory.md)
 - [Make HTTP requests with the HttpClient](httpclient.md)
-- [Use IHttpClientFactory to implement resilient HTTP requests](../../../architecture/microservices/implement-resilient-applications/use-httpclientfactory-to-implement-resilient-http-requests.md)
+- [Build resilient HTTP apps: Key development patterns](../../../core/resilience/http-resilience.md)
diff --git a/docs/standard/choosing-core-framework-server.md b/docs/standard/choosing-core-framework-server.md
@@ -1,7 +1,7 @@
 ---
 title: Choose between .NET and .NET Framework for server apps
 description: A guide to help you decide which implementation of .NET to use when building a server app.
-ms.date: 06/04/2024
+ms.date: 10/23/2024
 ms.custom: updateeachrelease
 ---
 # .NET vs. .NET Framework for server apps
@@ -27,7 +27,7 @@ There are two supported [.NET implementations](glossary.md#implementation-of-net
 
   There are many infrastructure platforms available. [Azure Service Fabric](https://azure.microsoft.com/services/service-fabric/) is designed for large and complex microservice systems. [Azure App Service](https://azure.microsoft.com/services/app-service/) is a good choice for stateless microservices. Microservices alternatives based on Docker fit any microservices approach, as explained in the next section (Supports Docker containers). All these platforms support .NET and make them ideal for hosting your microservices.
 
-  For more information about microservices architecture, see [.NET Microservices: Architecture for containerized .NET apps](../architecture/microservices/index.md).
+  For more information about microservices architecture, see [.NET Microservices: Architecture for containerized .NET apps](https://dotnet.microsoft.com/download/e-book/microservices-architecture/pdf).
 
 - **Supports Docker containers.**
 
@@ -87,4 +87,4 @@ As previously mentioned, the *.NET* implementation offers significant benefits f
 - [Porting from .NET Framework to .NET 5](../core/porting/index.md)
 - [Introduction to .NET and Docker](../core/docker/introduction.md)
 - [.NET implementations](../fundamentals/implementations.md)
-- [.NET Microservices. Architecture for Containerized .NET Applications](../architecture/microservices/index.md)
+- [.NET Microservices. Architecture for Containerized .NET Applications](https://dotnet.microsoft.com/download/e-book/microservices-architecture/pdf)
