20220928 1440

Author: WilliamDAssafMSFT

docs/relational-databases/performance/query-store-hints.md

@@ -101,21 +101,21 @@ When hints are applied, the following result set appears in the `StmtSimple` ele
 *   Queries will always execute where any opposing Query Store hints, that would otherwise cause an error, will be ignored.
 *   If Query Store hints contradict, SQL Server will not block query execution and Query Store hint will not be applied.
 *   Simple parameterization - Query Store hints are not supported for statements that qualify for simple parameterization.
-*   Forced parameterization - The RECOMPILE hint is not compatible with forced parameterization set at the database level. If the database has forced parameterization set, and the RECOMPILE hint is part of the hints string set in Query Store for a query, SQL Server will ignore the RECOMPILE hint and will apply any other hints if they are leveraged.
+*   Forced parameterization - The RECOMPILE hint is not compatible with forced parameterization set at the database level. If the database has forced parameterization set, and the RECOMPILE hint is part of the hints string set in Query Store for a query, SQL Server will ignore the RECOMPILE hint and will apply any other hints if they are applied.
     *    Additionally, SQL Server will issue a warning (error code 12461) stating that the RECOMPILE hint was ignored.
     *    For more information on forced parameterization use case considerations, see [Guidelines for Using Forced Parameterization](../query-processing-architecture-guide.md#forced-parameterization).
 *   Currently, Query Store hints can be applied against the primary replica of an Always On availability group.
-*   Manually-created Query Store hints are permenantly exempt from cleanup. The hint and the query will not be cleaned up from Query Store by the automatic retention of the capture policy. 
-    *   Queryies can be manually removed by users, which would also remove the associated Query Store hints.
-    *   Query Store hints automatically generated by the [CE Feedback](intelligent-query-processing-details.md#cardinality-estimation-ce-feedback) are subject to cleanup by the automatic retention of the capture policy. 
-    *   [DOP feedback](intelligent-query-processing-details.md#dop-feedback) and [memory grant feedback](intelligent-query-processing-details.md#memory-grant-feedback) shape query behavior without using Query Store hints. When queries are cleanup by automatic retnetion of the capture policy, DOP feedback and memory grant feedback data is also cleaned up. 
-    *   You can manually create the Query Store hint that CE feedback implemented, and then the query with the hint would no longer be subject to cleanup by the automatic retention of the capture policy.
+*   Manually created Query Store hints are permanently exempt from cleanup. The hint and the query will not be cleaned up from Query Store by the automatic retention of the capture policy. 
+    *   Queries can be manually removed by users, which would also remove the associated Query Store hints.
+    *   Query Store hints automatically generated by the [CE Feedback](intelligent-query-processing-details.md#cardinality-estimation-ce-feedback) are subject to clean up by the automatic retention of the capture policy. 
+    *   [DOP feedback](intelligent-query-processing-details.md#dop-feedback) and [memory grant feedback](intelligent-query-processing-details.md#memory-grant-feedback) shape query behavior without using Query Store hints. When queries are cleanup by automatic retention of the capture policy, DOP feedback and memory grant feedback data is also cleaned up. 
+    *   You can manually create the Query Store hint that CE feedback implemented, and then the query with the hint would no longer be subject to clean up by the automatic retention of the capture policy.
 
 
 ## Query Store hints best practices
 
 *    Complete index and statistics maintenance before evaluating queries for potential new Query Store hints.
-*    Test your application database on the latest [compatibility level](../../t-sql/statements/alter-database-transact-sql-compatibility-level.md), before leveraging Query Store hints.
+*    Test your application database on the latest [compatibility level](../../t-sql/statements/alter-database-transact-sql-compatibility-level.md) before using Query Store hints.
      * For example, Parameter Sensitive Plan (PSP) optimization was introduced in [!INCLUDE [sssql22-md](../../includes/sssql22-md.md)] (compatibility level 160), which leverages multiple active plans per query to address non-uniform data distributions. If your environment cannot use the latest compatibility level, Query Store hints using the RECOMPILE hint can be leveraged on any supporting compatibility level.
 *    Query Store hints override SQL Server query plan behavior. It is recommended to only leverage Query Store hints when it is necessary to address performance related issues.
 *    It is recommended to reevaluate Query Store hints, statement level hints, plan guides, and Query Store forced plans any time data distributions change and during database migrations projects. Changes in data distribution may cause Query Store hints to generate suboptimal execution plans.