Update azure_ai.py

azure_ai.py

@@ -22,7 +22,8 @@ documentation for projects with 50,000+ GitHub stars (e.g., FastAPI, LangChain,
 
 Your README output must:
 - Feel like a polished, production-grade open-source project
-- Use Mermaid diagrams: sequenceDiagram for API/data flow, flowchart LR for architecture. Dont use any HTML tags in Mermaid also Wrap the label in double quotes 
+- Use Mermaid diagrams: sequenceDiagram for API/data flow, flowchart LR for architecture. Dont use any HTML tags in Mermaid and Follow correct Syntax
+- Mermaid diagrams should change according to project working refer the sample one present in user input
 - Include shields.io badges, tables, and collapsible sections where appropriate
 - Be scannable: a developer should understand the project in under 60 seconds
 - Never truncate — every section must be fully written
@@ -64,8 +65,8 @@ Follow this EXACT structure and do not skip any section:
    - A Mermaid flowchart LR showing system components:
      ```mermaid
      flowchart LR
-         A["Input Layer]" --> B["Processing Layer"]
-         B --> C["Output Layer"]
+         A[Input Layer] --> B[Processing Layer]
+         B --> C[Output Layer]
      ```
    - A component breakdown table after the diagram:
      | Component | Role | Technology |
@@ -100,23 +101,18 @@ Follow this EXACT structure and do not skip any section:
      cp .env.example .env
      # Fill in your values
      ```
-
-9. Usage
-   - Basic example with code block
-   - Advanced example with code block
-
-10. Project Structure
+     
+9. Project Structure
     ```
     {repo_info['name']}/
     
     ```
+    
+10. Usage
+   - Basic example with code block
+   - Advanced example with code block
 
-11. Contributing
-    - 4-step git contribution guide in a bash code block
-
-12. License
-    - MIT License — Current Year {repo_info['name']} Contributors
-
+    
 Write the complete README now. Do not summarize, skip, or truncate any section.
 """