diff --git a/docs/relational-databases/performance/intelligent-query-processing-degree-parallelism-feedback.md b/docs/relational-databases/performance/intelligent-query-processing-degree-parallelism-feedback.md
index 40a5f83eaa5..96b419eb94f 100644
--- a/docs/relational-databases/performance/intelligent-query-processing-degree-parallelism-feedback.md
+++ b/docs/relational-databases/performance/intelligent-query-processing-degree-parallelism-feedback.md
@@ -41,7 +41,7 @@ Instead of incurring in the pains of an all-encompassing default or manual adjus
 
 Parallelism is often beneficial for reporting and analytical queries, or queries that otherwise handle large amounts of data. Conversely, OLTP-centric queries that are executed in parallel could experience performance issues when the time spent coordinating all threads outweighs the advantages of using a parallel plan. For more information, see [parallel plan execution](../../relational-databases/query-processing-architecture-guide.md#parallel-query-processing).
 
-- To enable DOP feedback, enable the `DOP_FEEDBACK` [database scoped configuration](../../t-sql/statements/alter-database-scoped-configuration-transact-sql.md#dop_feedback---on--off-) in a database. For example, in the user database:
+- DOP feedback is **disabled** by default. To enable DOP feedback, enable the `DOP_FEEDBACK` [database scoped configuration](../../t-sql/statements/alter-database-scoped-configuration-transact-sql.md#dop_feedback---on--off-) in a database. For example, in the user database:
 
     ```sql
     ALTER DATABASE SCOPED CONFIGURATION SET DOP_FEEDBACK = ON;