Fixed issues

Author: theresa-i

learn-pr/wwl-data-ai/implement-cicd-in-fabric/5-automate-cicd-using-fabric-apis.yml

@@ -8,6 +8,6 @@ metadata:
   author: wwlpublish
   ms.author: theresai
   ms.topic: unit
-durationInMinutes: 20
+durationInMinutes: 5
 content: |
   [!include[](includes/5-automate-cicd-using-fabric-apis.md)]

learn-pr/wwl-data-ai/implement-cicd-in-fabric/7-knowledge-check.yml

@@ -32,7 +32,7 @@ quiz:
     - content: To sync content between the workspace and Git, ensuring they have the same content.
       isCorrect: true
       explanation: Correct. Connecting a Fabric workspace to a Git repository allows for synchronization of content between the two, ensuring they have the same content.
-    - content: To allow multiple developers to work on the same code simultaneously without conflicts
+    - content: To allow multiple developers to work on the same code simultaneously without conflicts.
       isCorrect: false
       explanation: Incorrect. While Git does allow multiple developers to work simultaneously, the connection of a Fabric workspace to a Git repository isn't primarily for this purpose.
 

learn-pr/wwl-data-ai/implement-cicd-in-fabric/includes/2-understand-cicd.md

@@ -1,6 +1,5 @@
 When you and members of your team are each responsible developing and maintaining different parts of your Fabric environment, a best practice is to work in isolated development environments until you're ready to combine your development efforts and publish your changes to a particular pre-production environment. When you're ready to publish your changes, you need to make sure that your changes don't break existing code or interfere with changes made by other developers. There's also a need to ensure that code changes are saved and can be reverted if there are issues. The built-in continuous integration and continuous delivery capabilities in Fabric can help facilitate this.
 
-## Understand Continuous Integration and Continuous Delivery/Deployment (CI/CD)
  Continuous integration and continuous delivery is a process for integrating code contributions from multiple developers into a main codebase. Contributions are frequently committed, and automated processes build and test the new code. Code is continuously moving into production, reducing feature development time.
 
 ### Continuous integration

learn-pr/wwl-data-ai/implement-cicd-in-fabric/includes/3-implement-version-control-and-git-integration.md

@@ -31,7 +31,7 @@ To synchronize the workspace and repository:
     :::image type="content" source="../media/git-status.png" alt-text="Screenshot of uncommitted changes in workspace." :::
 
 ## Branching scenarios
-Changes that you make to a workspace when you're doing development work affect all other workspace users so it's best to work in isolation outside of shared workspaces. To keep your development work isolated from shared workspaces, you can develop using:
+Changes that you make to a workspace when you're doing development work affect all other workspace users so it's a best practice to work in isolation outside of shared workspaces. To keep your development work isolated from shared workspaces, you can develop using:
 - A separate, isolated workspace 
 - Client tools like Power BI Desktop for reports and semantic models or VS Code for Notebooks.
 
@@ -52,7 +52,7 @@ For development using a separate, isolated workspace:
 4. Then, *in Git*, create a **Pull Request (PR)** to pull the changes from your isolated branch into the main branch.  
 5. The main branch in Git will be updated once the PR is merged to the main branch. When you open the *shared* development workspace, you'll be prompted to synchronize the new content from Git with the shared development workspace. 
 
-Use client tools for development. The process is similar to that when developing in the Fabric web interface. 
+When using client tools for development, the process is similar to that when developing in the Fabric web interface. 
 
 1. Connect a development workspace to the main branch, following the instructions in the section on this page entitled "Connect a Fabric workspace to a Git repository".
 2. Clone the repository on your local machine.