From 4922e97dda7d0585ea2a217b96cfc3ea703fffef Mon Sep 17 00:00:00 2001
From: "polly-updater-bot[bot]"
 <138034000+polly-updater-bot[bot]@users.noreply.github.com>
Date: Tue, 17 Sep 2024 10:22:17 +0000
Subject: [PATCH] Update the code-snippets in the documentation

---
 docs/advanced/dependency-injection.md | 2 +-
 docs/advanced/performance.md          | 2 +-
 docs/advanced/telemetry.md            | 4 ++--
 docs/chaos/index.md                   | 2 +-
 docs/strategies/hedging.md            | 2 +-
 5 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/docs/advanced/dependency-injection.md b/docs/advanced/dependency-injection.md
index ade530c0cb3..5bbf3c68efb 100644
--- a/docs/advanced/dependency-injection.md
+++ b/docs/advanced/dependency-injection.md
@@ -127,7 +127,7 @@ Following the definition above, you can resolve the resilience pipelines using k
 
 <!-- snippet: di-keyed-services-use -->
 ```cs
-public class MyApi
+public sealed class MyApi
 {
     private readonly ResiliencePipeline _pipeline;
     private readonly ResiliencePipeline<HttpResponseMessage> _genericPipeline;
diff --git a/docs/advanced/performance.md b/docs/advanced/performance.md
index cd29968ce5a..afa23240537 100644
--- a/docs/advanced/performance.md
+++ b/docs/advanced/performance.md
@@ -135,7 +135,7 @@ Creating a resilience pipeline can be resource-intensive, so it's advisable not
 
 <!-- snippet: perf-reuse-pipelines -->
 ```cs
-public class MyApi
+public sealed class MyApi
 {
     private readonly ResiliencePipelineRegistry<string> _registry;
 
diff --git a/docs/advanced/telemetry.md b/docs/advanced/telemetry.md
index 44b82bdea9a..46ece083b3c 100644
--- a/docs/advanced/telemetry.md
+++ b/docs/advanced/telemetry.md
@@ -37,7 +37,7 @@ The `MyTelemetryListener` and `MyMeteringEnricher` is implemented as:
 
 <!-- snippet: telemetry-listeners -->
 ```cs
-internal class MyTelemetryListener : TelemetryListener
+internal sealed class MyTelemetryListener : TelemetryListener
 {
     public override void Write<TResult, TArgs>(in TelemetryEventArguments<TResult, TArgs> args)
     {
@@ -45,7 +45,7 @@ internal class MyTelemetryListener : TelemetryListener
     }
 }
 
-internal class MyMeteringEnricher : MeteringEnricher
+internal sealed class MyMeteringEnricher : MeteringEnricher
 {
     public override void Enrich<TResult, TArgs>(in EnrichmentContext<TResult, TArgs> context)
     {
diff --git a/docs/chaos/index.md b/docs/chaos/index.md
index 9112406bf6f..d114f23f0e4 100644
--- a/docs/chaos/index.md
+++ b/docs/chaos/index.md
@@ -300,7 +300,7 @@ In this approach, a helper extension method can be introduced to add a predefine
 <!-- snippet: chaos-extension -->
 ```cs
 // Options that represent the chaos pipeline
-public class MyChaosOptions
+public sealed class MyChaosOptions
 {
     public ChaosFaultStrategyOptions Fault { get; set; } = new()
     {
diff --git a/docs/strategies/hedging.md b/docs/strategies/hedging.md
index e64e1641dbf..49b37ba7105 100644
--- a/docs/strategies/hedging.md
+++ b/docs/strategies/hedging.md
@@ -658,7 +658,7 @@ A common use case is with [`DelegatingHandler`](https://learn.microsoft.com/aspn
 
 <!-- snippet: hedging-handler -->
 ```cs
-internal class HedgingHandler : DelegatingHandler
+internal sealed class HedgingHandler : DelegatingHandler
 {
     private readonly ResiliencePipeline<HttpResponseMessage> _pipeline;