Document service tags/environment (#4519)

Author: atovpeko

use-timescale/services/service-management.md

@@ -91,6 +91,24 @@ digest algorithm 5) are cryptographic authentication mechanisms. $CONSOLE_LONG
 uses SCRAM by default. It is more secure and strongly recommended. The MD5
 option is provided for compatibility with older clients.
 
+## Change the $SERVICE_SHORT environment
+
+In $CLOUD_LONG, you create $SERVICE_SHORTs for the following environments: 
+
+- Development $SERVICE_SHORTs: for less demanding tasks, such as ad hoc analytics, testing, or application building. Development $SERVICE_SHORTs have no delete protection. 
+- Production $SERVICE_SHORTs: for mission-critical applications like client-facing dashboards or APIs. Production $SERVICE_SHORTs have delete protection. 
+
+$CLOUD_LONG [applies upgrades differently][maintenance-upgrades] to development and production $SERVICE_SHORTs. 
+
+To change the environment of an existing $SERVICE_SHORT:
+
+<Procedure>
+
+1. In [$CONSOLE][services-portal], select the $SERVICE_SHORT to update.
+1. Click `Operations` > `Environment`, then change the tag under `Change service environment`.
+
+</Procedure>
+
 ## Pause a $SERVICE_SHORT
 
 You can pause a $SERVICE_SHORT if you want to stop it running temporarily. When you
@@ -103,3 +121,6 @@ that it is still available, and is ready to be restarted at any time.
 You can delete a $SERVICE_SHORT to remove it completely. This removes the $SERVICE_SHORT
 and its underlying data from the server. You cannot recover a deleted
 $SERVICE_SHORT.
+
+[maintenance-upgrades]: /use-timescale/:currentVersion:/upgrades/#minor-software-upgrades
+[services-portal]: https://console.cloud.timescale.com/dashboard/services

use-timescale/upgrades.md

@@ -39,7 +39,7 @@ After a maintenance upgrade, the DNS name remains the same. However, the IP addr
 ## Minor software upgrades
 
 If you do not [manually upgrade $TIMESCALE_DB][minor-manual-upgrade] for non-critical upgrades,
-$CLOUD_LONG performs upgrades automatically in the next available maintenance window. The upgrade is first applied to your $SERVICE_SHORTs tagged `#dev`, and three weeks later to those tagged `#prod`. [Subscribe][subscribe] to get an email notification before your `#prod` $SERVICE_SHORTs are upgraded. You can upgrade your `#prod` $SERVICE_SHORTs manually sooner, if needed. 
+$CLOUD_LONG performs upgrades automatically in the next available maintenance window. The upgrade is first applied to your $SERVICE_SHORTs tagged `#dev`, and three weeks later to those tagged `#prod`. [Subscribe][subscribe] to get an email notification before your `#prod` $SERVICE_SHORTs are upgraded. You can upgrade your `#prod` $SERVICE_SHORTs manually sooner, if needed. See [Service management][service-management] for how to manage $SERVICE_SHORT tags. 
 
 Most upgrades that occur during your maintenance windows do not require any downtime. This means that there is no 
 $SERVICE_SHORT outage during the upgrade. However, all connections and transactions in progress during the upgrade are 
@@ -238,3 +238,4 @@ To change your maintenance window:
 [hareplica]: /use-timescale/:currentVersion:/ha-replicas/high-availability/
 [readreplica]: /use-timescale/:currentVersion:/ha-replicas/read-scaling/
 [subscribe]: https://status.timescale.com/
+[service-management]: /use-timescale/:currentVersion:/services/service-management/#change-the-service-environment