diff --git a/docs/relational-databases/performance/intelligent-query-processing-details.md b/docs/relational-databases/performance/intelligent-query-processing-details.md
index 1826f9400d6..21004fe1372 100644
--- a/docs/relational-databases/performance/intelligent-query-processing-details.md
+++ b/docs/relational-databases/performance/intelligent-query-processing-details.md
@@ -73,8 +73,6 @@ Contrast the prior plan with the actual plan generated with interleaved executio
 
 MSTVF referencing statements in interleaved execution must currently be read-only and not part of a data modification operation. Also, MSTVFs are not eligible for interleaved execution if they do not use runtime constants.
 
-Using the query hint `OPTIMIZE FOR` parameters may not be eligible for interleaved execution and could disable the feature for the query.
-
 ### Interleaved execution benefits
 
 In general, the higher the skew between the estimated vs. actual number of rows, coupled with the number of downstream plan operations, the greater the performance impact.