Update optimize-search-partitions.md

Author: JV0812

docs/search/optimize-search-partitions.md

@@ -14,10 +14,6 @@ This example shows a customer that created three additional Partitions to separa
 
 ![data-by-environment](/img/search/optimize/data-by-environment.png)
 
-You can create partitions for both data tier and flex plans. By default, all data ingested into Sumo Logic will go to the Continuous Tier, unless you specific the data tier using the routing expression. Only data that goes to a partition can be assigned Frequent or Infrequent Tiers. For Continuos and Frequent tier data ingestion, costs will be incurred for ingesting the data into Sumo Logic. But for Infrequent tier data ingestion, there is no cost incurred for ingesting the data, whereas, pricing is determined by the scanned volume of insights and analytics. To learn more, refer to the [Data Tier Partitions](/docs/manage/partitions/data-tiers). 
-
-By contrast, with the Flex plan, there is no concept of configuring the data to a respective tier. All the data ingested in Flex plan will go as flex data, and pricing is determined by the scanned volume of insights and analytics with access to more default features like data forwarding, dashboards, monitors, scheduled searches, and scheduled views. To learn more about creating partitions with the Flex plan, refer to [Flex Partitions](/docs/manage/partitions/flex).
-
 Consider the following queries:
 
 | Query |  Partition Status | Path |
@@ -32,6 +28,10 @@ Consider the following queries:
 * **Query 3**. You can take advantage of Partitions without having to rewrite your existing queries. Sumo Logic's behind-the-scenes Query Rewriting, performed for queries run against data, is smart enough to understand that the scope of what you are looking for is included within `_index=prod`; therefore at runtime, it will rewrite the query as Query 2.
 * **Query 4**. We want to search for data that is in a custom Partition, as well as data that exists in the Default Index. However, query rewriting does not have the ability to OR indexes together. Instead, another behind-the-scenes feature, Inverse View Rewriting kicks in, we know that the data is NOT contained in the DEV and QA index, so those will be skipped.  This query will only scan the Prod index and the Default Index.
 
+You can create partitions for both data tier and flex plans. By default, all data ingested into Sumo Logic will go to the continuous tier unless you specify a different data tier using the routing expression. Only data that goes to a partition can be assigned to Frequent or Infrequent Tier. Costs will be incurred for ingesting the data into Sumo Logic for continuous and frequent tier data ingestion. However, for infrequent tier data ingestion, no cost is incurred for ingesting the data, whereas pricing is determined by the scanned volume of insights and analytics.  To learn more, refer to the [Data Tier Partitions](/docs/manage/partitions/data-tiers). 
+
+In contrast, the Flex plan does not involve configuring data into specific tiers. All data ingested under the Flex plan is classified as Flex data, and pricing is determined by the scanned volume of insights and analytics. This plan also provides access to additional default features, such as data forwarding, dashboards, monitors, scheduled searches, and scheduled views.  To learn more about creating partitions with the Flex plan, refer to the [Flex Partitions](/docs/manage/partitions/flex).
+
 ## What is Query Rewriting?
 
 Whenever possible, we rewrite a user's queries to perform better. We'll illustrate this using a simple example below:.