Fix URLs only, not fix text

Signed-off-by: maipbui <[email protected]>
sonic-net · Sep 8, 2022 · fe9d63a · fe9d63a
1 parent 7fe676c
commit fe9d63a
Show file tree

Hide file tree

Showing 12 changed files with 23 additions and 23 deletions.
diff --git a/doc/SONiC_202012_Release_Notes.md b/doc/SONiC_202012_Release_Notes.md
@@ -127,7 +127,7 @@ The SONiC Management Framework provides a unified UI stack, enabling SONiC to be
 This set of enhancements extends the framework, including (but not limited to) the following additions: -
 
 -	CLI: Usability enhancements, performance enhancements, User-document generation
--	Translib Infrastructure: Much of the UI infrastructure is separated out into a new repo (sonic-mgmt-common), de-coupling it from the UI code (which remains in the sonic-mgmt-framework repo). This allows the sonic-gnmi container (which also uses the infra) to be built and used independently from sonic-mgmt-framework. Other enhancements include support for RPC, YANG versioning, bulk calls (e.g. from gNMI), Authorization, and other code optimizations
+-	Translib Infrastructure: Much of the UI infrastructure is separated out into a new repo (sonic-mgmt-common), de-coupling it from the UI code (which remains in the sonic-mgmt-framework repo). This allows the sonic-telemetry container (which also uses the infra) to be built and used independently from sonic-mgmt-framework. Other enhancements include support for RPC, YANG versioning, bulk calls (e.g. from gNMI), Authorization, and other code optimizations
 -	CVL: This is an infrastructure component to perform UI validations. It is enhanced here to support Dynamic Port Breakout configuration dependency and for improved performance.
 -	Transformer: This is an infrastructure component to perform YANG tree to configuration object translations. Enhancements include support for more overloading functions, cascaded operations (for dynamic port breakout) and aliasing
 -	REST Server: Enhancements include RBAC, RESTCONF, YANG module discovery, statistics and other optimizations

diff --git a/doc/auto_techsupport_and_coredump_mgmt.md b/doc/auto_techsupport_and_coredump_mgmt.md
@@ -168,7 +168,7 @@ module sonic-auto_techsupport {
 
     yang-version 1.1;
 
-    namespace "http://github.com/sonic-net/sonic-auto_techsupport";
+    namespace "http://github.com/Azure/sonic-auto_techsupport";
     prefix auto_techsupport;
 
     import sonic-types {

diff --git a/doc/mgmt/Management Framework.md b/doc/mgmt/Management Framework.md
@@ -216,8 +216,8 @@ Management framework makes use of the translation library (Translib) written in
 #### 1.2.2 Container
 
 The management framework is designed to run in a single container named “sonic-mgmt-framework”. The container includes the REST server linked with Translib, and CLI process.
-The gNMI support requires the gNMI server which is provided as a part of sonic-gnmi container. We would like to rename this container as the sonic-gnmi container as now it can perform configurations as well through the gNMI server.
-Will introduce a new container sonic-mgmt-common to host the common code that is used both in the mgmt-framework and sonic-gnmi container. This new repo will compile into static libraries that will be used in the other two repos. This way sonic-gnmi repo can be compiled without the mgmt-framework being present in the code base.
+The gNMI support requires the gNMI server which is provided as a part of sonic-telemetry container. We would like to rename this container as the sonic-telemetry container as now it can perform configurations as well through the gNMI server.
+Will introduce a new container sonic-mgmt-common to host the common code that is used both in the mgmt-framework and sonic-telemetry container. This new repo will compile into static libraries that will be used in the other two repos. This way sonic-telemetry repo can be compiled without the mgmt-framework being present in the code base.
 
 ## 2 Functionality
 

diff --git a/doc/mgmt/SONiC_YANG_Model_Guidelines.md b/doc/mgmt/SONiC_YANG_Model_Guidelines.md
@@ -53,13 +53,13 @@ module sonic-acl {
 }
 ```
 
-### 3. Define namespace as "http://github.com/sonic-net/{model-name}".
+### 3. Define namespace as "http://github.com/Azure/{model-name}".
 
 Example :
 ####  YANG
 ```
 module sonic-acl {
-	namespace "http://github.com/sonic-net/sonic-acl";
+	namespace "http://github.com/Azure/sonic-acl";
 	.....
 	.....
 }
@@ -633,7 +633,7 @@ module sonic-port {
 
 ```
 module sonic-acl {
-	namespace "http://github.com/sonic-net/sonic-acl";
+	namespace "http://github.com/Azure/sonic-acl";
 	prefix sacl;
 	yang-version 1.1;
 

diff --git a/doc/mgmt/sonic-acl.yang b/doc/mgmt/sonic-acl.yang
@@ -1,5 +1,5 @@
 module sonic-acl {
-	namespace "http://github.com/sonic-net/sonic-acl";
+	namespace "http://github.com/Azure/sonic-acl";
 	prefix sacl;
 	yang-version 1.1;
 

diff --git a/doc/nvgre_tunnel/nvgre_tunnel.md b/doc/nvgre_tunnel/nvgre_tunnel.md
@@ -197,7 +197,7 @@ module sonic-nvgre-tunnel {
 
     yang-version 1.1;
 
-    namespace "http://github.com/sonic-net/sonic-nvgre-tunnel";
+    namespace "http://github.com/Azure/sonic-nvgre-tunnel";
     prefix nvgre;
 
     import ietf-inet-types {

diff --git a/doc/passw_hardening/hld_password_hardening.md b/doc/passw_hardening/hld_password_hardening.md
@@ -313,7 +313,7 @@ SPECIAL_CLASS                         = "True" / "False"
 //filename:  sonic-passw.yang
 module sonic-passwh {
     yang-version 1.1;
-    namespace "http://github.com/sonic-net/sonic-passwh";
+    namespace "http://github.com/Azure/sonic-passwh";
 	prefix passwh;
 
     description "PASSWORD HARDENING YANG Module for SONiC OS";

diff --git a/doc/pbh/pbh-design.md b/doc/pbh/pbh-design.md
@@ -1052,7 +1052,7 @@ module sonic-pbh {
 
     yang-version 1.1;
 
-    namespace "http://github.com/sonic-net/sonic-pbh";
+    namespace "http://github.com/Azure/sonic-pbh";
     prefix pbh;
 
     import ietf-inet-types {

diff --git a/doc/sonic-application-extension/img/docker-infra-concepts.svg b/doc/sonic-application-extension/img/docker-infra-concepts.svg
diff --git a/doc/sonic-application-extension/img/packages-json.svg b/doc/sonic-application-extension/img/packages-json.svg
diff --git a/doc/sonic-application-extension/sonic-application-extention-hld.md b/doc/sonic-application-extension/sonic-application-extention-hld.md
@@ -156,7 +156,7 @@ Basic definitions:
 There are three notions: *package*, *repository* and *registry*. A repository is a Docker registry (private or open like Docker Hub)
 repository with tagged images for specific package.
 
-In the above figure *sonic-net/sonic-dhcp-relay* and *sonic-net/sonic-snmp* are repositories with a set of images.
+In the above figure *Azure/sonic-dhcp-relay* and *Azure/sonic-snmp* are repositories with a set of images.
 
 ### SONiC Package
 
@@ -254,13 +254,13 @@ A sample of the content in JSON format:
     "installed-version": "1.0.0"
   },
   "dhcp-relay": {
-    "repository": "sonic-net/sonic-dhcp-relay",
+    "repository": "Azure/sonic-dhcp-relay",
     "description": "DHCP relay feature",
     "default-reference": "sha256:5d41c289942008211c2964bca72800f5c9d5ea5aa4057528da617fb36463d4ab",
     "status": "not-installed"
   },
   "snmp": {
-    "repository": "sonic-net/sonic-snmp",
+    "repository": "Azure/sonic-snmp",
     "description": "Simple Network Monitoring Protocol",
     "default-reference": "1.0.0",
     "status": "installed",

diff --git a/doc/syslog/syslog-design.md b/doc/syslog/syslog-design.md
@@ -466,7 +466,7 @@ module sonic-syslog {
 
     yang-version 1.1;
 
-    namespace "http://github.com/sonic-net/sonic-system-syslog";
+    namespace "http://github.com/Azure/sonic-system-syslog";
     prefix syslog;
 
     import ietf-inet-types {