addressed review comments

Author: AbhishekMallick-MS

articles/backup/backup-azure-files-faq.yml

@@ -194,24 +194,24 @@ sections:
           >The policy changes will affect only the recovery points created as part of the scheduled backup. For on-demand backups, retention is determined by the **Retain Till** value specified at the time of taking the backup.
 
       - question: |
-          What does the  duration attribute in Azure Files backup policy signify?
+          What does the duration attribute in Azure Files backup policy signify?
         answer: |
           The **duration** attribute helps to determine the timestamp for last backup of the day. 
 
-          For example, if the **start time** is “x AM” and **duration** is “y hours”, the backups will be scheduled between “x AM” and **schedule** attribute (x AM + y hours) as defined in the policy. This attribute enables you to ensure backups are only triggered during your working hours when there're frequent update operations on file share contents; therefore, taking multiple snapshots will safeguard data from any accidental changes.
+          For example, if the **start time** is “x AM” and **duration** is “y hours”, the backups will be scheduled between “x AM” and (x AM + y hours) based on the **schedule** attribute defined in the policy. This attribute enables you to ensure backups are only triggered during your working hours when there're frequent update operations on file share contents; therefore, taking multiple snapshots will safeguard data from any accidental changes.
 
       - question: |
           How are the backups scheduled based on the attributes - start time, schedule, and duration?
         answer: |
           For example, you created a policy with the following configuration:
 
           - **Start time**: 9 AM
-          - **Schedule**: Every 6 hours
+          - **Schedule**: Every 4 hours
           - **Duration**: 12 hours
 
-          Based on these values, the backup window is calculated as 9 AM – 9 AM + 12 hours, that is, 9 AM – 9 PM. Therefore, all backups will be scheduled within this window.
+          Based on these values, the backup window is calculated as 9 AM – (9 AM + 12 hours), that is, 9 AM – 9 PM. Therefore, all backups will be scheduled within this window.
 
-          The first backup of the day is triggered at the start time mentioned in the policy, that is, 9 AM, and the **schedule** determines the time difference between consecutive backups, that is, 6 hours. With this calculation, your backup schedule would be: 9 AM, 1 PM (9 AM + 6 hours), 5 PM (1 PM + 6 hours), and 9 PM (5 PM + 6 hours).
+          The first backup of the day is triggered at the start time mentioned in the policy, that is, 9 AM, and the **schedule** determines the time difference between consecutive backups, that is, 4 hours. With this calculation, your backup schedule would be: 9 AM, 1 PM (9 AM + 4 hours), 5 PM (1 PM + 4 hours), and 9 PM (5 PM + 4 hours).
 
           Since the end time of the backup window we calculated was 9 PM, no backup would be triggered after this time.
 
@@ -235,6 +235,8 @@ sections:
 
           Based on this configuration, the backup window will be: 12 PM – 3 AM (12 PM + 15 hours). Since the start and end times are falling on two different days, we recommend you adjust the **start time** or **duration** to ensure they are on the same day.
 
+          Let’s assume, you change the start time to 6 AM in the above configuration. Now, the backup window will be 6 AM – 9 PM (6 AM + 15 hours). This is a supported configuration.
+
       - question: |
           What’s the impact on the existing recovery points when I switch from “Daily” to “Hourly” frequency?
         answer: |
@@ -247,8 +249,6 @@ sections:
             - If daily retention is extended, the expiration date of the existing daily recovery points is updated according to the daily retention value configured in the new policy.
             - If daily retention is reduced, the existing daily recovery points and snapshots are marked for deletion in the next cleanup run job according to the daily retention value configured in the new policy, and then deleted.
 
-          Let’s assume, you change the start time to 6 AM in the above configuration. Now, the backup window will be 6 AM – 9 PM (6 AM + 15 hours). This is a supported configuration.
-
 additionalContent: |
 
   ## Next steps

articles/backup/manage-afs-backup.md

@@ -41,7 +41,7 @@ To create a new backup policy, follow these steps:
 
    :::image type="content" source="./media/manage-afs-backup/define-policy-type.png" alt-text="Screenshot showing to select Azure File Share as the policy type.":::
 
-1. As the **Backup policy** pane for **Azure File Share** opens, specify the policy name, backup frequency, and retention range for the recovery points to define the policy, and then select **OK**.
+1. As the **Backup policy** pane for **Azure File Share** opens, specify the policy name.
 
 1. In **Backup schedule**,  select an appropriate frequency for the backups - **Daily** or **Hourly**.