From b802395e168013d42ad9ecefeff3a29bb27c02e6 Mon Sep 17 00:00:00 2001
From: Shyam <69485234+shyam77git@users.noreply.github.com>
Date: Wed, 19 Jan 2022 13:30:26 -0800
Subject: [PATCH] Update Interface-Link-bring-up-sequence.md

Address review comments, added more details to 'Proposal' section, added 'Out of Scope' section
---
 doc/sfp-cmis/Interface-Link-bring-up-sequence.md | 5 +----
 1 file changed, 1 insertion(+), 4 deletions(-)

diff --git a/doc/sfp-cmis/Interface-Link-bring-up-sequence.md b/doc/sfp-cmis/Interface-Link-bring-up-sequence.md
index 15ad204602..35891d2597 100644
--- a/doc/sfp-cmis/Interface-Link-bring-up-sequence.md
+++ b/doc/sfp-cmis/Interface-Link-bring-up-sequence.md
@@ -142,14 +142,11 @@ Please refer to the  flow/sequence diagrams which covers the following required
 Following items are not in the scope of this document. They would be taken up separately
 1. xcvrd restart 
    - If the xcvrd goes for restart, then all the DB events will be replayed. 
-     Here the Datapath init/activate (for 400G), tx-disable register set (for 100G), will be a no-op if the optics is already in that state
-     
+     Here the Datapath init/activate (for 400G), tx-disable register set (for 100G), will be a no-op if the optics is already in that state 
 2. syncd/gbsyncd/swss docker container restart
    - Cleanup scenario - the host_tx_ready field in STATE-DB should be updated to “False” to respective ports that a PHY/NPU interface with
-   -
 3. CMIS API feature is not part of this design and the APIs will be used in this design. For CMIS HLD, Please refer to:
    https://github.com/Azure/SONiC/blob/9d480087243fd1158e785e3c2f4d35b73c6d1317/doc/sfp-cmis/cmis-init.md
-   
 4. Error handling of SAI attributes
    a) At present, If there is a set attribute failure, orch agent will exit. 
       Refer the error handling API : https://github.com/Azure/sonic-swss/blob/master/orchagent/orch.cpp#L885