service to application network

Author: pwright

input/images/overview.svg

@@ -7,7 +7,7 @@ While there are plans to create migration tooling, currently, the only way migra
 
 Terminology changes:
 
-* **service network**: Application network or just network
+* **application network**: Application network or just network
 * **service sync**: Services are not automatically available on other sites. You must create a *connector* on the site with the server process and a *listener* on the site with the client process. Also you must match the connector and listener with a *routing key* to expose a service.
 * **Skupper Custom Resources**: On non-Kubernetes sites, you can now define your network using YAML. The YAML format is similar to Kubernetes YAML.
 

input/overview/migrating.md

@@ -43,7 +43,7 @@ spec:
                 type:
                   type: string
                   description: |-
-                    Selected protocol for service networking. By default, its value is TCP, the only option available.
+                    Selected protocol for application networking. By default, its value is TCP, the only option available.
                 includeNotReadyPods:
                   description: |-
                     Advanced. If true, include server pods in the NotReady state. By default it is false.