From 4c735ca12ffd7c36ffaf5a9ba728c6941e31191e Mon Sep 17 00:00:00 2001
From: jaganbal-a <97986478+jaganbal-a@users.noreply.github.com>
Date: Thu, 20 Jan 2022 20:56:52 -0500
Subject: [PATCH] Update Interface-Link-bring-up-sequence.md

---
 doc/sfp-cmis/Interface-Link-bring-up-sequence.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/sfp-cmis/Interface-Link-bring-up-sequence.md b/doc/sfp-cmis/Interface-Link-bring-up-sequence.md
index 35891d2597..ac3273ea05 100644
--- a/doc/sfp-cmis/Interface-Link-bring-up-sequence.md
+++ b/doc/sfp-cmis/Interface-Link-bring-up-sequence.md
@@ -99,7 +99,7 @@ Interface link bring-up sequence and workflows for use-cases around it
 Have a determistic approach for Interface link bring-up sequence i.e. below sequence to be followed:
   1. Initialize and enable NPU Tx and Rx path
   2. For system with 'External' PHY: Initialize and enable PHY Tx and Rx on both line and host sides; ensure host side link is up 
-  3. Then only perform optics data path initialization/activation/Tx enable (for 400G) and Tx enable (for 100G) 
+  3. Then only perform optics data path initialization/activation/Tx enable (for CMIS complaint optical modules) and Tx enable (for SFF complaint optical modules) 
 
 # Proposal