Update servicestatus.md

Author: JarbasHorst

api-reference/v1.0/resources/servicestatus.md

@@ -51,17 +51,21 @@ Represents the tenant-level service status of the backup service.
 |:------|:------------|
 |disabled | Service is disabled. This is the default state. The service isn't enabled for the tenant.|
 |enabled | Service is enabled. A new protection policy can be created or modified and restore is allowed.|
-|protectionChangeLocked | Service is locked with no change in protection allowed. A new protection policy can't be created or updated. No new protection items can be added or removed.
-When does it happen?
-Scenario 1 : Tenant has no Active Service apps.
-In this case, if there are no active service apps found for the tenant, the feature status of the tenant will be changed to ProtectionChangeLocked from Enabled. To fix this, tenant needs to activate a service app and call the enable API for the same.
-Scenario 2 : Tenant has unhealthy billing profile
-In this case, when an unhealthy billing profile is found for a tenant, the feature status is automatically moved to "protectionChangeLocked" from "enabled", and the policies are deactivated right away. To resolve this, tenant needs to update the billing profile with a healthy one and wait for 24-48 hrs to get reflected.|
-|restoreLocked | Service is locked with no protection change and no restore. The protection policy can't be created or updated. No new protection items can be added or removed. No restore can be performed.
-When does it happen?
-When a tenant stays in the "ProtectionChangeLocked" for 30 days, the status changes from "protectionChangeLocked" to "restoreLocked", with this change, restore capabilities are blocked and billing gets stopped as well. To fix this , tenant needs to follow the specific steps depending on the scenarios it belongs to (1 or 2)|
+|protectionChangeLocked | Service is locked with no change in protection allowed. A new protection policy can't be created or updated. No new protection items can be added or removed.|
+|restoreLocked | Service is locked with no protection change and no restore. The protection policy can't be created or updated. No new protection items can be added or removed. No restore can be performed.|
 |unknownFutureValue | Evolvable enumeration sentinel value. Don't use.|
 
+#### protectionChangeLocked
+
+The following scenarios describe when a service is locked with no change in protection allowed:
+
+- **Scenario 1**: Tenant has no active service apps. If no active service apps are found for the tenant, the feature status of the tenant changes from `enabled` to `protectionChangeLocked`. To resolve this issue, the tenant needs to activate a service app and call the enable API.
+- **Scenario 2**: Tenant has an unhealthy billing profile. When an unhealthy billing profile is found for a tenant, the feature status is automatically moved from `enabled` to `protectionChangeLocked`, and the policies are deactivated right away. To resolve this issue, the tenant needs to update the billing profile with a healthy one and wait for 24-48 hours for the changes to take effect.
+
+#### restoreLocked
+
+When a tenant stays in the `protectionChangeLocked` status for 30 days, the status changes from `protectionChangeLocked` to `restoreLocked`. With this change, restore capabilities are blocked, and billing also stops. To resolve this issue, the tenant needs to follow the specific steps depending on the previous scenarios (1 or 2) it belongs to.
+
 ## Relationships
 
 None.