Mention connection between environment type and life cycle

website/docs/reference/environments.md

@@ -10,7 +10,7 @@ title: Environments
 :::
 ## Overview
 
-Environments represent different stages in your development lifecycle. They allow you to manage your product releases from local development to production. [Projects](/reference/projects) and [feature flags](/reference/feature-toggles) are accessible in all environments, but each environment has different configurations. This allows you to enable a feature flag in development or test without enabling it in production.
+Environments represent different stages in your development lifecycle. They allow you to manage your product releases from local development to production. [Projects](/reference/projects) and [feature flags](/reference/feature-toggles) are accessible in all environments, but each environment has different feature flag configurations. This allows you to enable a flag in development or test without enabling it in production.
 
 The default environments are **development** and **production**. Unleash instances created before version `4.3` also have an environment called **default**. [Enterprise](https://www.getunleash.io/pricing) customers can create, clone, deprecate, and delete environments.
 
@@ -24,7 +24,7 @@ Each environment has a name and one of the following types:
 - Pre-production
 - Production
 
-Environments of type production show additional confirmation prompts when making changes that may affect users. The default **production** environment is of type production.
+Receiving metrics in a given environment type affects a feature's [lifecycle stage](/reference/feature-toggles#feature-flag-lifecycle). For example, receiving metrics in a production environment moves the feature flag to the [live](/reference/feature-toggles#live) stage. Production environments also display additional confirmation prompts for changes that may impact users. The default **production** environment is of type production.
 
 ## Activation strategies
 

website/docs/reference/feature-toggles.mdx

@@ -95,23 +95,23 @@ These insights can help you improve the efficiency of your software development
 
 #### Initial
 
-The feature flag is created, but Unleash hasn't detected any metrics in any environments. Once Unleash receives metrics from a non-production environment, the flag moves to the [pre-live](#pre-live) stage.
+The feature flag is created, but Unleash hasn't detected any metrics in any environments. Once Unleash receives metrics from a [non-production environment](/reference/environments#environment-types), the flag moves to the [pre-live](#pre-live) stage.
 
 A feature stuck in an initial stage can indicate integration issues in pre-production setups. 
 
 #### Pre-live
 
-The feature flag has received metrics in a non-production environment or a production environment that is disabled. Too much time in the pre-live stage can suggest challenges in achieving production readiness. 
+The feature flag has received metrics in a non-production environment or a [production environment](/reference/environments#environment-types) that is disabled. Too much time in the pre-live stage can suggest challenges in achieving production readiness. 
 
 #### Live
 
-The first users have been exposed to the feature in a production environment. Once you have enough production usage data, you can mark the feature as completed. Marking the feature flag as complete does not affect any configuration; you decide whether to keep the feature, keep just one variant of it, or archive it entirely.
+The first users have been exposed to the feature in a [production environment](/reference/environments#environment-types). Once you have enough production usage data, you can mark the feature as completed. Marking the feature flag as complete does not affect any configuration; you decide whether to keep the feature, keep just one variant of it, or archive it entirely.
 
 This stage serves as a reminder to start cleaning up the feature toggle and removing it from the code. A feature flag stuck in the live stage can indicate difficulties in data gathering or decision-making.
 
 #### Completed
 
-The feature has been completed but Unleash still receives usage metrics in production. This is an indication that you should clean up the feature flag from your code before archiving it.
+The feature has been completed but Unleash still receives usage metrics in [production](/reference/environments#environment-types). This is an indication that you should clean up the feature flag from your code before archiving it.
 If you've accidentally marked the feature as completed, you can revert it to the [live](#live) stage.
 
 Too much time in the completed stage can indicate delays in decommissioning the feature and cleaning up resources.