update

Author: dingmeng-xue

articles/spring-apps/basic-standard/how-to-start-stop-service.md

@@ -29,7 +29,7 @@ The ability to stop and start your Azure Spring Apps service instance has the fo
 
 - You can stop and start your Azure Spring Apps service instance to help you save costs. However, stopping and then starting a service instance won't automatically fix system errors or recover invalid settings. For example, it cannot recover from an invalid virtual network configuration.
 - You can only start, view, or delete a stopped Azure Spring Apps service instance. You must start your service instance before performing any update operation, such as creating or scaling an app.
-- The state of a stopped Azure Spring Apps service instance is preserved for up to 90 days. If the service instance is stopped for more than 90 days, you cannot perform any operations on this instance except deleting it.
+- The state of a stopped Azure Spring Apps service instance is preserved for up to 90 days. If the service instance is stopped for more than 90 days, you cannot perform any operations on this instance except fetching settings or deleting it.
 - If an Azure Spring Apps service instance has been stopped or started successfully, you have to wait for at least 30 minutes to start or stop the instance again. However, if your last operation failed, you can try again without waiting.
 - For virtual network instances, the start operation may fail due to invalid virtual network configurations. For more information, see [Customer responsibilities for running Azure Spring Apps in a virtual network](./vnet-customer-responsibilities.md).