addressed PR review inputs

Author: AbhishekMallick-MS

articles/backup/azure-kubernetes-service-backup-overview.md

@@ -190,8 +190,8 @@ spec:
 Learn [how to use hooks during AKS backup](azure-kubernetes-service-cluster-backup.md#use-hooks-during-aks-backup).
 
   > [!NOTE]
-  > 1. During restore, backup extension waits for container to come up and then executes exec commands on them, defined in the restore hooks.
-  > 2. In case you are performing restore to the same namespace that was backed up, the restore hooks will not be executed as it only looks for new container that gets spawned. This is regardless of whether skip or patch policy is opted.
+  > - During restore, backup extension waits for container to come up and then executes exec commands on them, defined in the restore hooks.
+  > - In case you are performing restore to the same namespace that was backed up, the restore hooks will not be executed as it only looks for new container that gets spawned. This is regardless of whether skip or patch policy is opted.
 
 
 

articles/backup/azure-kubernetes-service-backup-troubleshoot.md

@@ -171,11 +171,11 @@ These error codes appear due to issues on the Backup Extension installed in the
 
 **Recommended action**: To address this, we recommend increasing the compute values allocated to this pod. By doing so, it will be automatically provisioned on a different node within your AKS cluster with ample compute resources available.
 
-The current value of compute for this pod is :
+The current value of compute for this pod is:
 
 resources.requests.cpu is 500m
 resources.requests.memory is 128Mi
-Kindly modify the memory allocation to 512Mi by updating the 'resources.requests.memory' parameter. If the issue persist, it is advisable to increase the 'resources.requests.cpu' parameter to 900m, post the memory allocation.You can increase the values for the parameters by following below steps:
+Kindly modify the memory allocation to 512Mi by updating the 'resources.requests.memory' parameter. If the issue persists, it is advisable to increase the 'resources.requests.cpu' parameter to 900m, post the memory allocation. You can increase the values for the parameters by following below steps:
 
 1. Navigate to the AKS cluster blade in the Azure portal.
 2. Click on "Extensions+Applications" and select "azure-aks-backup" extension.

articles/backup/azure-kubernetes-service-cluster-backup.md

@@ -212,23 +212,23 @@ To configure backups for AKS cluster:
 
 ### Backup configurations
 
-Azure Backup for AKS allows you define the application boundary within AKS cluster that you want to backup. You can use the filters that are available within backup configuration to choose the resources to back up and also to run custom hooks. The defined backup configuration are referenced by the value for **Backup Instance Name**. You have below filters available to define your application boundary:
+Azure Backup for AKS allows you define the application boundary within AKS cluster that you want to backup. You can use the filters that are available within backup configurations to choose the resources to back up and also to run custom hooks. The defined backup configuration are referenced by the value for **Backup Instance Name**. You have below filters available to define your application boundary:
 
 1. **Select Namespaces to backup**, you can either select **All** to back up all existing and future namespaces in the cluster, or you can select **Choose from list** to select specific namespaces for backup.
 
-     :::image type="content" source="./media/tutorial-configure-backup-aks/backup-instance-name.png" alt-text="Screenshot that shows how to select namespaces to include in the backup." lightbox="./media/tutorial-configure-backup-aks/backup-instance-name.png":::
+     :::image type="content" source="./media/azure-kubernetes-service-cluster-backup/backup-instance-name.png" alt-text="Screenshot that shows how to select namespaces to include in the backup." lightbox="./media/azure-kubernetes-service-cluster-backup/backup-instance-name.png":::
 
 2. Expand **Additional Resource Settings** to see filters that you can use to choose cluster resources to back up. You can choose to back up resources based on the following categories:
 
    - **Labels**: You can filter AKS resources by using [labels](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/) that you assign to types of resources. Enter labels in the form of key/value pairs. Combine multiple labels by using `AND` logic.
 
    For example, if you enter the labels `env=prod;tier!=web`, the process selects resources that have a label with the `env` key and the `prod` value, and a label with the `tier` key for which the value isn't `web`. 
 
-   - **API groups**: You can also include resources by providing the AKS API group and kind. For example, you can choose for backup AKS resources like Deployments. You can access the list of Kubernetes defined API Groups [here] (https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.30/)
+   - **API groups**: You can also include resources by providing the AKS API group and kind. For example, you can choose for backup AKS resources like Deployments. You can access the list of Kubernetes defined API Groups [here](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.30/).
 
    - **Other options**: You can enable or disable backup for cluster-scoped resources, persistent volumes, and secrets. By default, cluster-scoped resources and persistent volumes are enabled
 
-   :::image type="content" source="./media/tutorial-configure-backup-aks/cluster-scope-resources.png" alt-text="Screenshot that shows the Additional Resource Settings pane." lightbox="./media/tutorial-configure-backup-aks/cluster-scope-resources.png":::
+   :::image type="content" source="./media/azure-kubernetes-service-cluster-backup/cluster-scope-resources.png" alt-text="Screenshot that shows the Additional Resource Settings pane." lightbox="./media/azure-kubernetes-service-cluster-backup/cluster-scope-resources.png":::
 
    > [!NOTE]
    > All these resource settings are combined and applied via `AND` logic.