Merge pull request #285667 from vikramrajumsft/main

Fix chaos-studio-chaos-experiments.md in chaos-studio articles repo

Author: AnnaMHuff

articles/chaos-studio/chaos-studio-chaos-experiments.md

@@ -33,22 +33,21 @@ Chaos experiments can target resources in a different subscription than the expe
 
 ## Documenting chaos experiments
 
-There are several methods for documenting chaos engineering. One approach is to use work items in Azure DevOps Boards or in GitHub Projects. By creating dedicated work items for each experiment, you can track the details, progress, and outcomes of your experiments in a structured manner. This documentation can include information such as the purpose of the experiment, the expected outcomes, the steps followed, the resources involved, and any observations or learnings from the experiment.
-
-| Aspect         | Details                                                                                | Description     |
-|----------------|-------------------------------------------------------------------------------------------|-----------------|
-| Hypothesis     | Define the objective and expected outcomes of the experiment                              |                 |
-| Attack Layer   | Identify which part of the system will be subjected to chaos experiments (e.g., network, database, application layer). |                 |
-| Duration       | Specify the time frame for the chaos experiment.                                          |                 |
-| Target         | Determine the specific targets or components within the system.                           |                 |
-| Environment    | Define whether the experiment will be conducted in a production, staging, or development environment. |                 |
-| Observations   | Record any data or behavior observed during the experiment.                               |                 |
-| Results        | Summarize the findings and outcomes of the experiment.                                    |                 |
-| Action Items   | List any action items or steps to be taken based on the results.                          |                 |
-|                |                                                                                           |                 |
-
-The hypothesis is a crucial aspect of a chaos experiment as it defines the objective and expected outcomes of the experiment. It helps in testing the system's ability to handle unexpected disruptions effectively. By formulating a clear hypothesis, you can focus your experiment on specific areas of the system and gather meaningful data to evaluate its resilience. 
-By leveraging the features of Azure DevOps Boards or GitHub Projects, you can collaborate with your team, assign tasks, set due dates, and track the overall progress of your chaos engineering initiatives. This documentation serves as a reference for future analysis, sharing knowledge, and improving the resilience of your systems.
+There are several key aspects of your chaos experimentation process you can track and modify over time. One approach is to use work items in Azure Boards or in GitHub Projects. By creating dedicated work items for each experiment, you can track the details, progress, and outcomes of your experiments in a structured manner. This documentation can include information such as the purpose of the experiment, the expected outcomes, the steps followed, the resources involved, and any observations or learnings from the experiment.
+
+| Item         | Details                                                                                |
+|----------------|-------------------------------------------------------------------------------------------|
+| Hypothesis     | Define the objective and expected outcomes of the experiment                              |
+| Target Scope   | Identify which part of the system will be subjected to chaos experiments (e.g., network, database, application layer). |
+| Duration       | Specify the time frame for the chaos experiment.                                          |
+| Target         | Determine the specific targets or components within the system.                           |
+| Environment    | Define whether the experiment will be conducted in a production, staging, or development environment. |
+| Observations   | Record any data or behavior observed during the experiment.                               |
+| Results        | Summarize the findings and outcomes of the experiment.                                    |
+| Action Items   | List any action items or steps to be taken based on the results.                          |
+|                |                                                                                           |
+
+The **hypothesis** is a crucial aspect of a chaos experiment as it defines the objective and expected outcomes of the experiment. It helps in testing the system's ability to handle unexpected disruptions effectively. By formulating a clear hypothesis, you can focus your experiment on specific areas of the system and gather meaningful data to evaluate its resilience. By leveraging the features of Azure Boards or GitHub Projects, you can collaborate with your team, assign tasks, set due dates, and track the overall progress of your chaos engineering initiatives.
 
 ## Next steps
 Now that you understand what a chaos experiment is you're ready to: