simplified the content

Author: DocGailZhou

infra/samples/network_subnet_design.md

@@ -5,14 +5,14 @@ This guide explains how to use the sample Bicep program `network-subnet-design.b
 ## Purpose and Approach
 
 - **Sample File:** `infra/samples/network-subnet-design.bicep`
-- **Reusable Modules:** All code in `infra/modules/network` is designed to be composable and reusable. You should not need to modify code in the modules folder.
+- **Reusable Modules:** All code in `infra/modules/network` is designed to be reusable. You should not need to modify code in the modules folder.
 - **Custom Network File:** For your own solution, create a `network.bicep` in `infra/modules/` that represents your specific network design, using the modules as building blocks.
 
 ## How to Use the Sample
 
 - The sample demonstrates how to deploy a virtual network, subnets, NSGs, Azure Bastion Host, and Jumpbox VM using parameters and reusable modules.
-- You can deploy the sample independently to validate your network design before integrating it into your main solution, modify the infra/modules/network.bicep using the validated and tested design. 
 - The sample is parameterized, so you can easily adjust subnet names, address spaces, NSG rules, and delegations.
+- You can design and validate your network design with  `infra/samples/network-subnet-design.bicep`, then integrate the code by updating `infra/modules/network.bicep` with your tested design. 
 
 ## Key Features in the Sample
 
@@ -26,8 +26,6 @@ This guide explains how to use the sample Bicep program `network-subnet-design.b
   - Example: The `web` subnet allows HTTPS inbound from anywhere; the `app` subnet allows traffic from the `web` subnet, etc.
 - **Bastion and Jumpbox:**
   - Optional Azure Bastion Host and Jumpbox VM are included for secure management access.
-- **Composability:**
-  - All modules in `infra/modules/network` are designed to be reused without modification.
 
 ## Example Workflow
 
@@ -38,7 +36,7 @@ This guide explains how to use the sample Bicep program `network-subnet-design.b
 3. **Deploy the Sample:**
    - Use Azure Developer CLI (`azd`) or Azure CLI to deploy the sample and validate your design.
 4. **Integrate into Solution:**
-   - Once validated, use the same approach to build your own `network.bicep` in `infra/modules/` for your production solution.
+   - Once validated, use the same approach to build your own `network.bicep` in `infra/modules/` for your solution. Test your solution with i`nfra/main.bicep`. 
 
 ## Example Directory Structure
 
@@ -49,7 +47,7 @@ infra/
       ... (reusable modules)
     network.bicep   # <-- your custom network design
   samples/
-    network-subnet-design.bicep  # <-- sample for reference
+    network-subnet-design.bicep  # <-- reference
 ```
 
 ## Best Practices
@@ -58,12 +56,3 @@ infra/
 - Reuse modules as much as possible to reduce duplication and improve maintainability.
 - Clearly document subnet address ranges, NSG rules, and any special configuration in comments.
 - Validate your design with Azure best practices for security, scalability, and manageability.
-
-## Next Steps
-
-- Use this document as a living reference. Update it as your solution and requirements evolve.
-- Refer to the sample and module documentation for advanced scenarios (e.g., private endpoints, delegations, Bastion, Jumpbox).
-
----
-
-*This guide is based on the latest comments and structure in `network-subnet-design.bicep`. Update as your solution matures.*