From 9e09f84e6d292d610bcc9a6c56f8933a0e833b3f Mon Sep 17 00:00:00 2001
From: Mencken Davidson <76002183+menckend@users.noreply.github.com>
Date: Wed, 24 Jul 2024 20:43:16 -0400
Subject: [PATCH] Update 1_3_3.md

---
 pages/1/3(ecmp-symmetric)/1_3_3.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/pages/1/3(ecmp-symmetric)/1_3_3.md b/pages/1/3(ecmp-symmetric)/1_3_3.md
index 71f9fe4..d6d4513 100644
--- a/pages/1/3(ecmp-symmetric)/1_3_3.md
+++ b/pages/1/3(ecmp-symmetric)/1_3_3.md
@@ -51,8 +51,8 @@ We could also base our evaluation on a comparison of node A/B's symmetric-perime
 
 Now that we can *identify* each of the potential equal-cost paths in a bidirectionally-consistent manner, we need to figure out how to decide *which* of those paths we want to use for any given bidirectional flow-pair.  We want this decision process to:
 - Be bi-directionally consistent
-- To load-share (at the endpoint-pair level) across all of the equal-cost paths
-- To provide resiliency in the event of failure on any of the three paths
+- Load-share (at the endpoint-pair level) across all of the equal-cost paths
+- Provide resiliency in the event of failure on any of the three paths
 
 To do this, we need an evaluation function that provides the same results when its two input parameters are reversed and provides a (near) uniform distribution across three output values.