Rename remaining VCS references to Slice
Change-Id: I82f674120c3f77275a0d48dea648e2c78a4b3022
diff --git a/advanced/appfilter.rst b/advanced/appfilter.rst
index 6f49769..de0ede7 100644
--- a/advanced/appfilter.rst
+++ b/advanced/appfilter.rst
@@ -10,7 +10,7 @@
application endpoint is reachable or not, but also what maximum bitrate and traffic
class should be associated with that endpoint.
-A VCS may have a total of five user-defined application endpoints associated with it. Logically
+A Slice may have a total of five user-defined application endpoints associated with it. Logically
this could be one application with five endpoints, five applications with one endpoint
each, or any other combination that is less than or equal to five endpoints total.
@@ -32,15 +32,15 @@
maximum bitrate is per-device to the application; it is not the sum of all devices to the
application.
-Adding Applications to VCSes
-----------------------------
+Adding Applications to Slices
+-----------------------------
-Each VCS has an application filter, which is a list of applications. Each entry
+Each Slice has an application filter, which is a list of applications. Each entry
in this list has a priority and an allow|deny setting. Keep in mind that the total
-number of endpoints for all applications attached to the VCS must be less than or
+number of endpoints for all applications attached to the Slice must be less than or
equal to five.
-Also configurable for the VCS is the default-behavior, which will automatically
+Also configurable for the Slice is the default-behavior, which will automatically
be evaluated at the lowest priority, only taking effect if no other rule matches.
The default behavior does not count against the 5-endpoint limit.
diff --git a/edge_deployment/connectivity_service_update.rst b/edge_deployment/connectivity_service_update.rst
index d0b5429..0069a22 100644
--- a/edge_deployment/connectivity_service_update.rst
+++ b/edge_deployment/connectivity_service_update.rst
@@ -100,14 +100,15 @@
been assigned to the Enterprise. Link in the IP-Domain that was created previously, and
attach it to the site.
-#. Create a VCS. Select an appropriate template for the VCS. Link in the Device-Group,
+#. Create a Slice. Select an appropriate template for the Slice. Link in the Device-Group,
AP-List, and UPF that was created previously.
-#. Repeat the steps above as necessary for each VCS and for each Site that belongs to
+#. Repeat the steps above as necessary for each Slice and for each Site that belongs to
the enterprise.
+#. If the `Subscriber Proxy` is to be used, then create a default enterprise named
+ `defaultent` and a default site within that enterprise named
+ `defaultent-defaultsite`.
+
.. note:: This workflow does not address creating applications, as application filtering is
not part of the Aether-1.5 feature set.
-
-.. note:: This workflow does not address creating default sites, default device groups, or
- default VCSes, as subscriber-proxy based subscriber-learning is not enabled at this time.
diff --git a/operations/images/aether-roc-vcs-monitor.png b/operations/images/aether-roc-slice-monitor.png
similarity index 100%
rename from operations/images/aether-roc-vcs-monitor.png
rename to operations/images/aether-roc-slice-monitor.png
Binary files differ
diff --git a/operations/monitor.rst b/operations/monitor.rst
index 23fbee3..638b1d3 100644
--- a/operations/monitor.rst
+++ b/operations/monitor.rst
@@ -57,7 +57,7 @@
* Clicking on the down arrow expands each panel
-.. image:: images/aether-roc-vcs-monitor.png
+.. image:: images/aether-roc-slice-monitor.png
:width: 920
:alt: Slice Monitor View with Connectivity and Performance Charts
