Fix arrows

docs/migration-v8.md

@@ -157,8 +157,8 @@ IAsyncPolicy retryPolicy = Policy.Handle<Exception>().WaitAndRetryAsync(3, _ =>
 IAsyncPolicy timeoutPolicy = Policy.TimeoutAsync(TimeSpan.FromSeconds(3));
 
 // Wrap the policies. The policies are executed in the following order (i.e. Last-In-First-Out):
-// 1. Retry << outer
-// 2. Timeout << inner
+// 1. Retry <== outer
+// 2. Timeout <== inner
 IAsyncPolicy wrappedPolicy = Policy.WrapAsync(retryPolicy, timeoutPolicy);
 ```
 <!-- endSnippet -->
@@ -170,8 +170,8 @@ In v8, there's no need to use policy wrap explicitly. Instead, policy wrapping i
 <!-- snippet: migration-policy-wrap-v8 -->
 ```cs
 // The "PolicyWrap" is integrated directly. Strategies are executed in the same order as they were added (i.e. First-In-First-Out):
-// 1. Retry << outer
-// 2. Timeout << outer
+// 1. Retry <== outer
+// 2. Timeout <== outer
 ResiliencePipeline pipeline = new ResiliencePipelineBuilder()
     .AddRetry(new()
     {

src/Snippets/Docs/Migration.Wrap.cs

@@ -11,8 +11,8 @@ public static void PolicyWrap_V7()
         IAsyncPolicy timeoutPolicy = Policy.TimeoutAsync(TimeSpan.FromSeconds(3));
 
         // Wrap the policies. The policies are executed in the following order (i.e. Last-In-First-Out):
-        // 1. Retry << outer
-        // 2. Timeout << inner
+        // 1. Retry <== outer
+        // 2. Timeout <== inner
         IAsyncPolicy wrappedPolicy = Policy.WrapAsync(retryPolicy, timeoutPolicy);
 
         #endregion
@@ -23,8 +23,8 @@ public static void PolicyWrap_V8()
         #region migration-policy-wrap-v8
 
         // The "PolicyWrap" is integrated directly. Strategies are executed in the same order as they were added (i.e. First-In-First-Out):
-        // 1. Retry << outer
-        // 2. Timeout << outer
+        // 1. Retry <== outer
+        // 2. Timeout <== outer
         ResiliencePipeline pipeline = new ResiliencePipelineBuilder()
             .AddRetry(new()
             {