change all links from gh-pages to master

Signed-off-by: Guohan Lu <[email protected]>

doc/warm-reboot/open_issues.md

@@ -92,7 +92,7 @@ Both approaches have been under development and testing. Current status:
 
 ## Idempotent libsairedis API
 ### Design doc:
-[SONiC libsairedis API idempotence support](https://github.com/Azure/SONiC/blob/gh-pages/doc/warm-reboot/sai_redis_api_idempotence.md)
+[SONiC libsairedis API idempotence support](https://github.com/Azure/SONiC/blob/master/doc/warm-reboot/sai_redis_api_idempotence.md)
 ### Draft code changes:
 [libsairedis code changes](https://github.com/Azure/sonic-sairedis/compare/master...jipanyang:idempotent)
 ### Current status:

doc/watermarks_HLD.md

@@ -67,7 +67,7 @@ This document describes the high level design of the watermark feature.
 ## 1.1 System Chart
 Following diagram describes a top level overview of the architecture:
 
-![](https://github.com/mykolaf/SONiC/blob/gh-pages/images/watermark_HLD/SystemOverview.png)
+![](https://github.com/mykolaf/SONiC/blob/master/images/watermark_HLD/SystemOverview.png)
 
 ## 1.2 Modules description
 ### 1.2.1 gRPC
@@ -102,7 +102,7 @@ Regular user is able to query the persistent watermark. Regular user is able to
 
 When one regular user and the streaming telemetry coexist, they do not interfere with each other. Their behaviors stay the same as described above. So the software should be able to handle the following situations and return the correct watermark values to each user:
 
-![](https://github.com/mykolaf/SONiC/blob/gh-pages/images/watermark_HLD/timeline2.png)
+![](https://github.com/mykolaf/SONiC/blob/master/images/watermark_HLD/timeline2.png)
 
 
 t0 - clear user watermark event
@@ -337,7 +337,7 @@ Examples of virtual paths:
 
 #### 4.1 Watermark general flow
 
-![](https://github.com/mykolaf/SONiC/blob/gh-pages/images/watermark_HLD/WM_general.png)
+![](https://github.com/mykolaf/SONiC/blob/master/images/watermark_HLD/WM_general.png)
 
 The core components are the flex counter, watermark orch, DB, CLI. 
 
@@ -353,13 +353,13 @@ The Cli reads the watermarks from the tables, formats and outputs it.
 
 #### 4.2 Resetting the telemetry period flow
 
-![](https://github.com/mykolaf/SONiC/blob/gh-pages/images/watermark_HLD/WM_period.PNG)
+![](https://github.com/mykolaf/SONiC/blob/master/images/watermark_HLD/WM_period.PNG)
 
 The watermark orch handles notifications on changes in WATERMARK_TABLE in config DB. The new interval will be assigned to the timer during the timer handling, so the orch will reset the interval only when the current timer expires.
 
 #### 4.3 Cli flow
 
-![](https://github.com/mykolaf/SONiC/blob/gh-pages/images/watermark_HLD/WM_cli.png)
+![](https://github.com/mykolaf/SONiC/blob/master/images/watermark_HLD/WM_cli.png)
 
 ### 5 Open questions
 

doc/xrcvd/transceiver-monitor-hld.md

@@ -10,7 +10,7 @@
 ## About This Manual ##
 
 This document is intend to provide general information about the Transceiver and Sensor Monitoring implementation.
-The requirement is described in [Sensor and Transceiver Info Monitoring Requirement.](https://github.com/Azure/SONiC/blob/gh-pages/doc/OIDsforSensorandTransciver.MD)
+The requirement is described in [Sensor and Transceiver Info Monitoring Requirement.](https://github.com/Azure/SONiC/blob/master/doc/OIDsforSensorandTransciver.MD)
 
 
 ## 1. Xcvrd design ##
@@ -120,7 +120,7 @@ A timer will be started to periodically refresh the DOM sensor information .
 
 Detailed flow as showed in below chart: 
 
-![](https://github.com/Azure/SONiC/blob/gh-pages/images/transceiver_monitoring_hld/xcvrd_flow.svg)
+![](https://github.com/Azure/SONiC/blob/master/images/transceiver_monitoring_hld/xcvrd_flow.svg)
 
 ## 2. SNMP Agent Change ##
 
@@ -155,7 +155,7 @@ Another entPhySensorTable which is defined in [Entity Sensor MIB(RFC3433)](https
 | 1.3.6.1.2.1.47.1.1.1.1.2.index | entPhysicalDescr | Show interfaces alias | DOM RX Power Sensor for DOM RX Power Sensor for Ethernet29/1 |
 
 
-More detailed information about new table and new OIDs are described in [Sensor and Transceiver Info Monitoring Requirement](https://github.com/Azure/SONiC/blob/gh-pages/doc/OIDsforSensorandTransciver.MD#transceiver-requirements-entity-mib).
+More detailed information about new table and new OIDs are described in [Sensor and Transceiver Info Monitoring Requirement](https://github.com/Azure/SONiC/blob/master/doc/OIDsforSensorandTransciver.MD#transceiver-requirements-entity-mib).
 
 ### 2.2 New connection to STATE_DB ###