Added how to delete VCHs and download certs in UI (#1293)

docs/user_doc/vic_vsphere_admin/access_h5_ui.md

@@ -2,7 +2,7 @@
 
 If you have installed the HTML5 plug-in for vSphere Integrated Containers, you can find information about your vSphere Integrated Containers deployment in the HTML5 vSphere Client.
 
-**IMPORTANT**: Do not use the vSphere Client to perform operations on virtual container hosts or container VMs. Specifically, using the vSphere Client to power off, power on, or delete the VCH vApp or VCH endpoint VM can cause vSphere Integrated Containers Engine to not function correctly. Always use `vic-machine` to perform operations on VCHs. The vSphere Client does not allow you to delete container VMs, but do not use the vSphere Client to power container VMs on or off. Always use Docker commands to perform operations on containers. 
+**IMPORTANT**: Do not perform operations on virtual container hosts (VCHs) or container VMs in the vSphere Client inventory views. Specifically, using the vSphere Client inventory views to power off, power on, or delete the VCH resource pool or VCH endpoint VM can cause vSphere Integrated Containers Engine to not function correctly. Always use the vSphere Integrated Containers plug-in for the HTML5 vSphere Client or `vic-machine` to perform operations on VCHs. The vSphere Client does not allow you to delete container VMs, but do not use the vSphere Client to power container VMs on or off. Always use Docker commands to perform operations on containers. 
 
 **NOTE**: More functionality will be added to the vSphere Integrated Containers view in future releases.
 
@@ -29,7 +29,10 @@ If you have installed the HTML5 plug-in for vSphere Integrated Containers, you c
     - Indicates that the VCH is running correctly.
     - Displays the `DOCKER_HOST` environment variable that container developers use to connect to this VCH.
     - Provides the link to the VCH Admin Portal for this VCH.
+5. (Optional) Click the 3 vertical dots next to a VCH.
 
+    - Select **Delete** to remove the VCH. You can only remove VCHs that were deployed by using the same version of vSphere Integrated Containers Engine as is used by the vSphere Integrated Containers plug-in for vSphere Client.  
+    - Select **Download VCH certificate** to download the server certificate for the VCH. Container developers might require the server certificate when they run Docker commands in `--tlsverify` client mode, if you use certificates that are not signed by a trusted certificate authority. 
 5. Select the **Containers** tab.
 
     The **Containers** tab shows information about all of the container VMs that are running in this vCenter Server instance, for all VCHs:

docs/user_doc/vic_vsphere_admin/remove_vch.md

@@ -1,6 +1,8 @@
 # Delete Virtual Container Hosts #
 
-You delete virtual container hosts (VCHs) by using the `vic-machine delete` command.
+You delete virtual container hosts (VCHs) by using the `vic-machine delete` command. 
+
+You can also delete VCHs by using the vSphere Integrated Containers plug-in for the HTML5 vSphere Client. For information about using the plug-in, see [View All VCH and Container Information in the HTML5 vSphere Client](access_h5_ui.md).
 
 The `vic-machine delete` includes one option in addition to the [Common `vic-machine` Options](common_vic_options.md), `--force`.
 

docs/user_doc/vic_vsphere_admin/vch_portlet_ui.md

@@ -2,7 +2,7 @@
 
 After you have installed the client plug-ins for vSphere Integrated Containers, you can find information about individual virtual container hosts (VCHs) and container VMs in the HTML5 vSphere Client or the Flex-based vSphere Web Client.
 
-**IMPORTANT**: Do not use the vSphere Client to perform operations on virtual container hosts or container VMs. Specifically, using the vSphere Client to power off, power on, or delete the VCH vApp or VCH endpoint VM can cause vSphere Integrated Containers Engine to not function correctly. Always use `vic-machine` to perform operations on VCHs. The vSphere Client does not allow you to delete container VMs, but do not use the vSphere Client to power container VMs on or off. Always use Docker commands to perform operations on containers. 
+**IMPORTANT**: Do not perform operations on virtual container hosts (VCHs) or container VMs in the vSphere Client inventory views. Specifically, using the vSphere Client inventory views to power off, power on, or delete the VCH resource pool or VCH endpoint VM can cause vSphere Integrated Containers Engine to not function correctly. Always use the vSphere Integrated Containers plug-in for the HTML5 vSphere Client or `vic-machine` to perform operations on VCHs. The vSphere Client does not allow you to delete container VMs, but do not use the vSphere Client to power container VMs on or off. Always use Docker commands to perform operations on containers. 
 
 **Prerequisites**
 

docs/user_doc/vic_vsphere_admin/verify_vch_deployment.md

@@ -2,7 +2,7 @@
 
 After you have deployed a virtual container host (VCH), you can verify the deployment by connecting a Docker client to the VCH and running Docker operations. You can check the results in the vSphere Client or vSphere Web Client.
 
-**IMPORTANT**: Do not use the vSphere Client to perform operations on virtual container hosts or container VMs. Specifically, using the vSphere Client to power off, power on, or delete the VCH vApp or VCH endpoint VM can cause vSphere Integrated Containers Engine to not function correctly. Always use `vic-machine` to perform operations on VCHs. The vSphere Client does not allow you to delete container VMs, but do not use the vSphere Client to power container VMs on or off. Always use Docker commands to perform operations on containers. 
+**IMPORTANT**: Do not perform operations on virtual container hosts (VCHs) or container VMs in the vSphere Client inventory views. Specifically, using the vSphere Client inventory views to power off, power on, or delete the VCH resource pool or VCH endpoint VM can cause vSphere Integrated Containers Engine to not function correctly. Always use the vSphere Integrated Containers plug-in for the HTML5 vSphere Client or `vic-machine` to perform operations on VCHs. The vSphere Client does not allow you to delete container VMs, but do not use the vSphere Client to power container VMs on or off. Always use Docker commands to perform operations on containers. 
 
 **Prerequisites**
 
@@ -11,7 +11,6 @@ After you have deployed a virtual container host (VCH), you can verify the deplo
 - If you deployed the VCH to vCenter Server, connect a vSphere Client to that vCenter Server instance.
 - If you deployed the VCH to an ESXi host, connect a vSphere Client to that host.
 
-
 **Procedure**    
 
 1. View the VCH appliance in the vSphere Client or vSphere Client.
@@ -49,4 +48,8 @@ After you have deployed a virtual container host (VCH), you can verify the deplo
     - vCenter Server: Go to **Storage** and select the datastore that you designated as the image store. 
     - ESXi host: Click the **Summary** tab for the ESXi host, right-click the datastore that you designated as the image store, and select **Browse Datastore**. 
 
-     At the top-level of the datastore, you should see a folder for every container that you run. The folders contain the container VM files.
+     At the top-level of the datastore, you should see a folder for every container that you run. The folders contain the container VM files.
+
+**What to Do Next**
+
+If you deployed the HTML5 plug-in for the vSphere Client, you can see information about VCHs and containers in the Virtual Container Hosts view of the plug-in. For information about how to access the plug-in, see [View All VCH and Container Information in the HTML5 vSphere Client](access_h5_ui.md).