From b41e4aa269e843a3f8706ea9b9ff4e1e22fb7e14 Mon Sep 17 00:00:00 2001
From: Guillaume Mulocher <gmulocher@arista.com>
Date: Mon, 22 Jul 2024 14:39:40 +0200
Subject: [PATCH] Apply suggestions from code review

Co-authored-by: Claus Holbech <holbech@arista.com>
---
 .../arista/avd/roles/eos_designs/docs/how-to/wan.md           | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/ansible_collections/arista/avd/roles/eos_designs/docs/how-to/wan.md b/ansible_collections/arista/avd/roles/eos_designs/docs/how-to/wan.md
index 496db80fc16..dab40eb6b1e 100644
--- a/ansible_collections/arista/avd/roles/eos_designs/docs/how-to/wan.md
+++ b/ansible_collections/arista/avd/roles/eos_designs/docs/how-to/wan.md
@@ -576,10 +576,12 @@ interface Ethernet3
 An internet-exit policy of type `zscaler` leverages the following AVD data model to generate the target configuration.
 
 AVD supports up to three tunnels (primary, secondary, tertiary).
+AVD `eos_designs` will fetch Zscaler integration information from Cloudvision.
 
 ```yaml
+# Variables used by eos_designs to connect to Cloudvision
 cv_server: <cloudvision_ip>
-cv_token: <cloudvision_token>
+cv_token: <service account token as defined on CloudVision. This value should be using Ansible Vault>
 ```
 
 For each `zscaler` type Internet-policies, AVD uses the `cv_pathinfder_internet_exit_policies[name=<POLICY-NAME>].zscaler` dictionary and the `zscaler_endpoints` in combination with the `l3_interfaces.cv_pathfinder_internet_exit.policies[name=<POLICY-NAME>].tunnel_interface_numbers` to generate the internet-exit configuration.