Revise Targeting Overview

Author: adams85

website/docs/targeting/targeting-overview.mdx

@@ -6,9 +6,9 @@ description: Overview of the ConfigCat targeting feature with examples.
 
 Targeting allows you to enable or disable a feature for specific users or groups of users in your application. Typical use cases are:
 
-- Beta testing
-- A/B testing
-- Phased rollouts, canary releases
+- [Beta testing](../../glossary#beta-testing)
+- [A/B testing](../../glossary#ab-testing)
+- [Phased rollouts, canary releases](../../glossary#canary-release)
 
 ## How does it work?
 
@@ -37,7 +37,8 @@ simplicity because feature flags are the most common type of settings.
 ### Targeting Rule
 
 A _Targeting Rule_ consists of a collection of conditions and a value to serve. If the conditions are met (the Targeting
-Rule _matches_), the value is served to the user. More about [Targeting Rules here](../targeting-rule/targeting-rule-overview).
+Rule _matches_), the value is served, i.e. returned as the result of the feature flag evaluation. More about
+Targeting Rules [here](../targeting-rule/targeting-rule-overview).
 
 ### Condition
 
@@ -49,7 +50,7 @@ A _condition_ is a logical expression that can be evaluated to true or false. Th
 
 _Percentage Options_ are used to split users into groups that will receive a specific value for the feature flag.
 The groups are allocated based on the ratio of the percentages. Percentage Options are often used for A/B testing or
-phased rollouts. More about [Percentage Options here](../percentage-options).
+phased rollouts. More about Percentage Options [here](../percentage-options).
 
 ### "To all users" / "To all other" / "To unidentified" value
 
@@ -63,27 +64,27 @@ value will be returned in case the SDK fails to fetch the config or some other e
 
 ### User Object
 
-A _User Object_ is a collection of _user attributes_ that describe the properties of a user. Referencing these attributes
-in conditions allows you to define rules for targeting users. More about the [User Object here](../user-object).
+A _User Object_ is a collection of _user attributes_ that store the properties of a user. Referencing these attributes
+in conditions allows you to define rules for targeting users. More about the User Object [here](../user-object).
 
 ## Examples
 
 ### Phased rollout / Canary release / Percentage rollout Scenario
 
 #### Context
 
-Our demo company, Whisker Co. is about to release a new feature called `Park Weather Info`. The stakeholders want to make
-sure that releasing the new feature will go smoothly and it will be received well by the customers.
+Our demo company, Whisker Co. is about to release a new feature called **Park Weather Info**. The stakeholders want to make
+sure that the release of the new feature goes smoothly and it is received well by the customers.
 
 #### Goal
 
 To make sure that the new feature is working as expected before releasing it to everyone, we initially want to make the
-feature available to the employees and to `20%` of the customers only.
+feature available to the employees and to 20% of the customers only.
 
 #### Solution
 
-Let's create a feature flag called `Enable Park Weather Info` with a Targeting Rule that matches the employees at
-Whisker Co. and Percentage Options set to `20%` `ON` and `80%` `OFF` for the rest of the users (i.e. for the customers).
+Let's create a feature flag called **Enable Park Weather Info** with a Targeting Rule that matches the employees at
+Whisker Co. and Percentage Options set to **20% ON** and **80% OFF** for the rest of the users (i.e. for the customers).
 
 Here is what such a feature flag looks like on the Dashboard:
 ![Phased rollout Example](../../static/assets/targeting/targeting-overview/phased-rollout.png)