Replaced Figure in "Redundant Top-of-Rack Switch Deployment Considerations"

Updated Patchset 1 comments Signed-off-by: Juanita-Balaraj <juanita.balaraj@windriver.com> Change-Id: I4fa551b9133e4c0ef21719323bacba3cfdee1373 (cherry picked from commit 41cf08b09d)
2022-02-28 17:10:23 -05:00
parent 55f8b3ccc9
commit 1e49e46341
2 changed files with 1 additions and 1 deletions
--- a/doc/source/planning/kubernetes/redundant-top-of-rack-switch-deployment-considerations.rst
+++ b/doc/source/planning/kubernetes/redundant-top-of-rack-switch-deployment-considerations.rst
@@ -23,7 +23,7 @@ switches are normally active, providing full bandwidth to the |LAG|. If there
 are multiple failed links on both switches, at least one connection in each
 aggregate pair is still functional. If one switch fails, the other continues to
 provide connections for all |LAG| links that are operational on that switch.
-For more about configuring |VPC|, refer to your switch documentation.
+For more information about configuring |VPC|, refer to your switch documentation.

 You can use an active/standby failover model for the switches, but at a cost to
 overall reliability. If there are multiple failed links on both switches, then
--- a/doc/source/shared/figures/planning/jow1438030468959.png
+++ b/doc/source/shared/figures/planning/jow1438030468959.png