updates from acrolinx review

Author: petender

learn-pr/wwl-azure/introduction-agentic-devops-microsoft-tools-azure/6-knowledge-check.yml

@@ -22,7 +22,7 @@ quiz:
       explanation: "Deterministic, scripted execution is the defining characteristic of traditional automation, not agentic capabilities."
     - content: "It observes intermediate results and adapts its plan to reach a defined goal."
       isCorrect: true
-      explanation: "The observe-reason-act loop — combined with goal orientation and tool invocation — is what distinguishes agents from scripted automation."
+      explanation: "The observe-reason-act loop, combined with goal orientation and tool invocation, is what distinguishes agents from scripted automation."
     - content: "It can only suggest actions without executing them."
       isCorrect: false
       explanation: "Agentic capabilities span a full autonomy spectrum; many can execute actions, not only suggest them."
@@ -36,19 +36,19 @@ quiz:
       explanation: "Reversible operations with low blast radius and high frequency are suitable for autonomous execution, and work item assignment meets all three criteria."
     - content: "Inform only, because agents should never interact with project management data."
       isCorrect: false
-      explanation: "Inform is unnecessarily restrictive for this task. Agents can interact with Boards data; the question is how much autonomy is appropriate."
+      explanation: "Inform is restrictive for this task. Agents can interact with Boards data; the question is how much autonomy is appropriate."
   - content: "Which of the following DevOps operations must always retain a mandatory human authorization step regardless of agent maturity?"
     choices:
     - content: "Generating a pull request description for an infrastructure change."
       isCorrect: false
       explanation: "PR description generation is informational. No state is changed until a human opens the PR."
-    - content: "Creating RBAC role assignments in a production Azure subscription."
+    - content: "Creating RBAC (Role Based Access Control) role assignments in a production Azure subscription."
       isCorrect: true
-      explanation: "RBAC changes in production have low reversibility and compliance implications that require documented human authorization."
+      explanation: "RBAC (Role Based Access Control)changes in production have low reversibility and compliance implications that require documented human authorization."
     - content: "Summarizing the previous week's pipeline failure history."
       isCorrect: false
-      explanation: "This is a read-only, Inform-level operation that carries no blast radius or reversibility risk."
-  - content: "A platform team is designing their agentic DevOps deployment. They want to allow agents to generate and validate Bicep templates but require human review before applying changes to non-production environments. Which autonomy level does this describe?"
+      explanation: "This Inform-level operation is read-only, which carries no blast radius or reversibility risk."
+  - content: "A platform team is designing their agentic DevOps deployment. They want to allow agents to generate and validate Bicep templates but require human review before applying changes to nonproduction environments. Which autonomy level does this describe?"
     choices:
     - content: "Inform"
       isCorrect: false
@@ -58,15 +58,15 @@ quiz:
       explanation: "Execute autonomously means no per-step confirmation is required. This scenario explicitly requires human review before execution."
     - content: "Execute on approval"
       isCorrect: true
-      explanation: "Execute on approval means the agent prepares the execution plan and waits for explicit human confirmation before proceeding — matching this scenario exactly."
+      explanation: "Execute on approval means the agent prepares the execution plan and waits for explicit human confirmation before proceeding. Exactly matching this scenario."
   - content: "What is the primary reason to implement audit logging for agent-initiated Azure resource operations from the start of an agentic DevOps pilot?"
     choices:
     - content: "To prevent agents from making any changes to Azure resources during the pilot period."
       isCorrect: false
-      explanation: "Audit logging records actions; it doesn't block them. Preventing changes is handled by authorization scoping and approval gates."
+      explanation: "Audit logging records actions; it doesn't block them. Authorization scoping and approval gates prevent changes."
     - content: "To create the compliance baseline and feedback mechanism needed to responsibly expand agent autonomy over time."
       isCorrect: true
       explanation: "Audit logs serve two purposes: they satisfy compliance requirements and they provide the evidence that builds confidence for expanding autonomy as agent behavior is validated."
     - content: "To ensure that all agent actions are reviewed by a security team before they take effect."
       isCorrect: false
-      explanation: "Pre-flight review is handled by approval gates, not audit logs. Audit logs record what happened, enabling post-hoc review and incident investigation."
+      explanation: "Approval gates handle preflight review, not audit logs. Audit logs record what happened, enabling post-hoc review and incident investigation."

learn-pr/wwl-azure/introduction-agentic-devops-microsoft-tools-azure/includes/4-set-autonomy-boundaries-human-control.md

@@ -1,8 +1,9 @@
 Identifying high-value agentic opportunities is the easier half of the problem. The harder half is deciding exactly how much autonomy to grant for each one. And also building the guardrails that keep your production environment safe when agents operate within it.
 
-The engineers who get this wrong tend to fall into one of two failure modes: 
-- they lock down agents so tightly that the only value delivered is autocomplete-level suggestions, 
-- or they extend autonomous execution to actions whose blast radius they haven't carefully analyzed. 
+The engineers who get this concept wrong tend to fall into one of two failure modes:
+
+- **locked-down agents**: agents are locked so tightly, that the only value delivered is autocomplete-level suggestions. 
+- **autonomous execution**: agents run actions autonomously, without carefully analyzing impact.
 
 Both failures undermine adoption and erode trust. The goal is a calibrated model that matches autonomy level to reversibility, blast radius, and regulatory context.
 
@@ -17,7 +18,7 @@ Not all agentic actions carry the same operational weight. A useful way to class
 | **Execute on approval** | Prepares execution plan and waits for explicit confirmation | Review plan and authorize each step | Create a work item, update a variable group, and generate and apply IaC changes to a non-production environment |
 | **Execute autonomously** | Takes action through the full sequence without per-step confirmation | Define scope, monitor outcomes, and receive summary | Assign and triage incoming bug reports, run read-only API queries, and generate unit tests for new functions |
 
-Most of your day-to-day agentic operations will sit at **Inform** and **Suggest** for the first months. That's not a technical or adoption limitation. It allows your team to build up confidence and trust in agent behavior and develop the observability instrumentation to audit what agents do.
+Most of your day-to-day agentic operations will sit at **Inform** and **Suggest** for the first months. This approach is not a technical or adoption limitation. It allows your team to build up confidence and trust in agent behavior and develop the observability instrumentation to audit what agents do.
 
 ## Classify actions by reversibility and blast radius
 
@@ -36,7 +37,7 @@ Combine these dimensions and you get a quick classification model:
 | Low | Low | Execute on approval |
 | Low | Medium or High | Suggest only — human executes |
 
-**Never grant autonomous execution** to actions that combine low reversibility with any meaningful blast radius. Production deployments, secret or credential operations, network security group modifications, role assignment changes, and policy exceptions all fall in this quadrant regardless of how well-tested your agent instructions are.
+**Never grant autonomous execution** to actions that combine low reversibility with any meaningful blast radius. Several examples fall in this quadrant, such as production deployments, and how you handle secret or credential operations. Or think of network security group modifications or role assignment changes. Regardless of how well-tested your agent instructions are, keep human oversight as guardrail for these.
 
 ## Define human control points for production-facing operations
 

learn-pr/wwl-azure/introduction-agentic-devops-microsoft-tools-azure/includes/7-summary.md

@@ -4,11 +4,11 @@ You've now defined that layer precisely, mapped where it delivers value across t
 
 ## Key concepts from this module
 
-- An agent is distinguished from automation by goal orientation, tool invocation, and adaptive observe-reason-act loops. These properties let agents handle multi-source, multi-step tasks that require context synthesis rather than scripted execution.
-- The Microsoft platform provides agentic capabilities across a spectrum: from GitHub Copilot suggestions and agent mode, to Azure Copilot's specialized operational agents, to Azure DevOps AI features embedded directly in daily workflow surfaces.
-- The DevOps phases most amenable to early agentic adoption are plan/track work, code review, pipeline failure triage, and operational observability — tasks that are high-frequency, information-intensive, and produce reversible or read-only outcomes.
-- Autonomy levels should be matched to reversibility and blast radius. Low reversibility and high blast radius operations — production deployments, credential operations, RBAC changes, policy exceptions — require human authorization regardless of agent maturity.
-- Observability and audit logging for agent-initiated actions are required from day one, not added later. They form the compliance baseline and the feedback mechanism for responsibly expanding autonomy over time.
+- **Agents vs. automation**: Agents are goal-oriented, invoke tools dynamically, and adapt through observe-reason-act loops. This lets them handle complex, multi-step tasks requiring context synthesis instead of scripted steps.
+- **Microsoft's agentic spectrum**: GitHub Copilot, Azure Copilot agents, Azure DevOps AI, and MCP extensibility provide agentic capabilities across different surfaces.
+- **High-value DevOps phases**: Plan/track, code review, pipeline triage, and observability are best suited for early adoption—they're frequent, information-rich, and low-risk.
+- **Autonomy matching**: Tie autonomy levels to reversibility and blast radius. High-risk operations (deployments, credentials, role assigments, policy changes) always require human approval.
+- **Observability from day one**: Log and audit all agent actions. This ensures compliance and provides feedback for safely increasing autonomy over time.
 
 ## Next steps