Clarity edits and add art

Author: ecfan

articles/logic-apps/connect-virtual-network-vnet-isolated-environment-overview.md

@@ -124,6 +124,10 @@ When you create your ISE, you can choose to use either internal or external acce
 
 * **External**: Public endpoints permit calls to logic apps in your ISE where you can view and access inputs and outputs from logic apps' runs history *from outside your virtual network*. If you use network security groups (NSGs), make sure they're set up with inbound rules to allow access to the run history's inputs and outputs. For more information, see [Enable access for ISE](../logic-apps/connect-virtual-network-vnet-isolated-environment.md#enable-access).
 
+To determine whether your ISE uses an internal or external access endpoint, on your ISE's menu, under **Settings**, select **Properties**, and find the **Access endpoint** property:
+
+![Find ISE access endpoint](./media/connect-virtual-network-vnet-isolated-environment-overview/find-ise-access-endpoint.png)
+
 <a name="create-integration-account-environment"></a>
 
 ## Integration accounts with ISE

articles/logic-apps/media/connect-virtual-network-vnet-isolated-environment-overview/find-ise-access-endpoint.png

@@ -20,7 +20,7 @@ For real-time event monitoring and richer debugging, set up diagnostics logging
 > you can view and access inputs and outputs from logic app's runs history *only from inside your virtual network*. Make sure that you have network 
 > connectivity between the private endpoints and the computer from where you want to access runs history. For example, your client computer can exist 
 > inside the ISE's virtual network or inside a virtual network that's connected to the ISE's virtual network, for example, through peering or a virtual 
-> private network. For more information, see [ISE endpoint access](../logic-apps/connect-virtual-network-vnet-isolated-environment-overview.md#endpoint-access).
+> private network. For more information, see [ISE endpoint access](../logic-apps/connect-virtual-network-vnet-isolated-environment-overview.md#endpoint-access). 
 
 <a name="review-runs-history"></a>