Update logs-to-metrics.md

Author: JV0812

docs/metrics/logs-to-metrics.md

@@ -85,9 +85,9 @@ You cannot use a scheduled view or an index in the scope of a Logs-to-Metrics ru
 
 ### Using Logs-to-Metrics for partitions not included in default scope
 
-In the data tier model, frequent and infrequent partitions are excluded from the default search scope. If your organization is configured for the flex pricing model, you can selectively choose which partitions to include or exclude from the [default search scope](/docs/manage/partitions/flex/faq/#how-can-i-optimize-my-query-using-default-scope).
+In the data tier model, frequent and infrequent partitions are excluded from the default search scope. While, if your organization is configured for the flex pricing model, you can selectively choose which partitions to include or exclude from the [default search scope](/docs/manage/partitions/flex/faq/#how-can-i-optimize-my-query-using-default-scope).
 
-For cases involving partitions that fall outside the default scope, you can create a Logs-to-Metrics rule for the scope of frequent tier partition, infrequent tier partition, or for the partitions excluded in the flex pricing model. To do this, set the rule using the same log search scope as the partition where the data resides. 
+For cases involving partitions that fall outside the default scope, you can create a Logs-to-Metrics rule for the frequent tier partition, infrequent tier partition, or for the partitions excluded in the flex pricing model. To do this, set the rule using the same log search scope as the partition where the data resides. 
 
 For example, if you have a partition with the index `_index=foo`, and its routing expression is `_sourceCategory=foo`, you should use the same routing expression, `_sourceCategory=foo`, when scoping the Logs-to-Metrics rule.