update tier case

Author: serdec

docs/en/cloud/manage/jan2025_faq/plan_migrations.md

@@ -77,7 +77,7 @@ The `tier` field has been removed from the service object as there is no more di
 This will affect the objects returned by the `POST`, `GET`, and `PATCH` service requests. Therefore, any code that consumes these APIs may need to be adjusted to handle these changes.
 
 The number of replicas each service will be created with defaults to 3 for the Scale and Enterprise tiers, while it defaults to 1 for the Basic tier.
-For the Scale and the `ENTERPRISE` tiers it is possible to adjust it by passing a `numReplicas` field in the service creation request. 
+For the Scale and the Enterprise tiers it is possible to adjust it by passing a `numReplicas` field in the service creation request. 
 The value of the `numReplicas` field must be between 2 and 20 for the first service in a warehouse. Services that are created in an existing warehouse can have a number of replicas as low as 1.
 
 ### What changes should the users make if using the existing Terraform provider for automation?
@@ -91,7 +91,7 @@ After the migration, the `tier` field is no longer accepted, and references to i
 Users will also be able to specify the `num_replicas` field as a property of the service resource.
 
 The number of replicas each service will be created with defaults to 3 for the Scale and Enterprise tiers, while it defaults to 1 for the Basic tier.
-For the Scale and the `ENTERPRISE` tiers, it is possible to adjust it by passing a `numReplicas` field in the service creation request. 
+For the Scale and the Enterprise tiers, it is possible to adjust it by passing a `numReplicas` field in the service creation request. 
 The value of the `num_replicas` filed must be between 2 and 20 for the first service in a warehouse. Services that are created in an existing warehouse can have a number of replicas as low as 1.
 
 ### Will users have to make any changes to the database access?