From 6585540c679c822caa7ffd5795fb9767c1c57892 Mon Sep 17 00:00:00 2001
From: Martin Tomka <martintomka@microsoft.com>
Date: Mon, 24 Jul 2023 08:14:48 +0200
Subject: [PATCH] use strong for highlitght

---
 src/Polly.Core/ResilienceStrategy.cs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/Polly.Core/ResilienceStrategy.cs b/src/Polly.Core/ResilienceStrategy.cs
index 7ce23cd0660..4157a871acf 100644
--- a/src/Polly.Core/ResilienceStrategy.cs
+++ b/src/Polly.Core/ResilienceStrategy.cs
@@ -27,7 +27,7 @@ public abstract partial class ResilienceStrategy
     /// An instance of pending <see cref="ValueTask"/> for asynchronous executions or completed <see cref="ValueTask"/> task for synchronous exexutions.
     /// </returns>
     /// <remarks>
-    /// <c>This method is called for both synchronous and asynchronous execution flows.</c>
+    /// <strong>This method is called for both synchronous and asynchronous execution flows.</strong>
     /// <para>
     /// You can use <see cref="ResilienceContext.IsSynchronous"/> to dermine wheether the <paramref name="callback"/> is synchronous or asynchronous one.
     /// This is useful when the custom strategy behaves differently in each execution flow. In general, for most strategies, the implementation