Updates

Author: williamzhao87

articles/communication-services/concepts/router/distribution-concepts.md

@@ -7,7 +7,7 @@ manager: bgao
 services: azure-communication-services
 
 ms.author: williamzhao
-ms.date: 05/04/2022
+ms.date: 05/06/2022
 ms.topic: conceptual
 ms.service: azure-communication-services
 ---
@@ -68,7 +68,7 @@ When a Scoring Rule isn't provided, this distribution mode will use the default
 ### Default Label Matching
 For calculating a score based on the job's labels, we increment the `Match Score` by 1 for every worker label that matches a corresponding label on the job and then divide by the total number of labels on the job. Therefore, the more labels that matched, the higher a worker's `Match Score`.  The final `Match Score` will always be a value between 0 and 1.
 
-#### Example
+##### Example
 Job 1:
 ```json
 {
@@ -115,8 +115,6 @@ Worker B's match score = 1 (for matching english language label) / 2 (total numb
 Worker C's match score = 1 (for matching english language label) / 2 (total number of labels) = 0.5
 ```
 
-Explanation:
-
 Worker A would be matched first.  Next, Worker B or Worker C would be matched, depending on who was available for a longer time, since the match score is tied.
 
 ### Default Worker Selector Matching
@@ -125,7 +123,7 @@ In the case where the job also contains worker selectors, we'll calculate the `M
 #### Equal/NotEqual Label Operators
 If the worker selector has the `LabelOperator` `Equal` or `NotEqual`, we increment the score by 1 for each job label that matches that worker selector, in a similar manner as the `Label Matching` above. 
 
-#### Example
+##### Example
 Job 2:
 ```json
 {
@@ -172,14 +170,13 @@ Worker E's match score = 1 (for matching department selector) + 1 (for matching
 Worker F's match score = 1 (for segment not equal to vip) / 2 (total number of labels) = 0.5
 ```
 
-Explanation:
-
 Worker E would be matched first.  Next, Worker D or Worker F would be matched, depending on who was available for a longer time, since the match score is tied.
 
 #### Other Label Operators
 For worker selectors using operators that compare by magnitude (GreaterThan/GreaterThanEqual/LessThan/LessThanEqual), we'll increment the worker's `Match Score` by an amount calculated using the logistic function (See Fig 1).  The calculation is based on how much the worker's label value exceeds the worker selector's value or a lesser amount if it doesn't exceed the worker selector's value. Therefore, the more worker selector values the worker exceeds, and the greater the degree to which it does so, the higher a worker's score will be.
 
 :::image type="content" source="../media/router/logistic-function.png" alt-text="Fig 1. Logistic function.":::
+
 Fig 1. Logistic function
 
 The following function is used for GreaterThan or GreaterThanEqual operators:
@@ -245,6 +242,4 @@ Worker H's match score = (1 + 1 / (1 + e^-((15 - 10) / 10)) + 1 / (1 + e^-((10 -
 Worker I's match score = (1 + 1 / (1 + e^-((10 - 10) / 10)) + 1 / (1 + e^-((10 - 9) / 10))) / 3 = 0.675
 ```
 
-Explanation:
-
 All three workers match the worker selectors on the job and are eligible to work on it.  However, we can see that Worker H exceeds the "sales" worker selector's value by a margin of 5.  Meanwhile, Worker I only exceeds the cost worker selector's value by a margin of 1.  Worker G doesn't exceed any of the worker selector's values at all.  Therefore, Worker H would be matched first, followed by Worker I and finally Worker G would be matched last.