Doc(eos_designs,eos_cli_config_gen): Update roles documentation (#6464)

Author: carl-baillargeon

ansible_collections/arista/avd/roles/eos_cli_config_gen/README.md

@@ -12,12 +12,11 @@ title: Ansible Collection Role eos_cli_config_gen
 
 ## Overview
 
-**eos_cli_config_gen**, is a role that generates eos cli syntax and device documentation.
+**eos_cli_config_gen**, is a role that generates EOS CLI configuration and device documentation.
 
 The **eos_cli_config_gen** role:
 
 - Designed to generate the intended configuration offline, without relying on switch current state information.
-- Facilitates the evaluation of the configuration prior to deployment with tools like [Batfish](https://www.batfish.org/)
 - Facilitates the evaluation of the configuration post deployment with [anta_runner](../anta_runner/README.md) role.
 
 ## Role Inputs and Outputs
@@ -34,13 +33,13 @@ Figure 1 below provides a visualization of the roles inputs, and outputs and tas
 **Outputs:**
 
 - EOS configuration in CLI format.
-- Device Documentation in Markdown format.
+- Device documentation in Markdown format.
 
 **Tasks:**
 
-1. Import device structured configuration from YAML file unless `structured_config` flag is set by `eos_designs`.
+1. Load and validate input variables according to the EOS Config schema.
 2. Generate EOS configuration in CLI format.
-3. Generate Device Documentation in Markdown format.
+3. Generate device documentation in Markdown format.
 
 ## Requirements
 

ansible_collections/arista/avd/roles/eos_designs/README.md

@@ -44,26 +44,26 @@ To understand the interaction between `eos_designs` input variables and `eos_cli
 **Outputs:**
 
 - A structured EOS configuration file in YAML format. This provides the following benefits:
-  - Leverage the structured data to create eos CLI configuration.
+  - Leverage the structured data to create EOS CLI configuration.
   - Leverage the structured data to create end-user documentation.
   - Leverage the structured data for pre and post-fabric validation.
 - Fabric Documentation in Markdown format.
 - Leaf and Spine Topology summary in CSV format.
 
 **Tasks:**
 
-1. Set AVD facts.
-2. Generate YAML file with host variables (Optional for debugging/development with tag -> debug).
-3. Set device configuration facts.
-4. Write structured device configuration to YAML file.
-5. Include device structured configuration that was previously generated.
+1. Template and validate input variables according to the AVD Design schema.
+2. Generate AVD facts.
+3. Generate the structured configuration for each device.
+4. Write the structured configurations to files.
+5. Optionally return the structured configurations as Ansible facts.
 6. Generate fabric documentation in Markdown format.
 7. Generate fabric point-to-point links summary in CSV format.
 8. Generate fabric physical topology summary in CSV format.
 
 ## Reference Designs
 
-The following reference design types are included in the roles default variables:
+The following reference design types are included in the role's default variables:
 
 - L3LS EVPN: Layer 3 Leaf Spine with VXLAN EVPN
 - L2LS: Layer 2 Leaf Spine