Update query-profiling-infrastructure.md

Author: MikeRayMSFT

docs/relational-databases/performance/query-profiling-infrastructure.md

@@ -119,7 +119,7 @@ WITH (MAX_MEMORY=4096 KB,
 
 A new DMF [sys.dm_exec_query_plan_stats](../../relational-databases/system-dynamic-management-views/sys-dm-exec-query-plan-stats-transact-sql.md) is introduced to return the equivalent of the last known actual execution plan for most queries, and is called *last query plan statistics*. The last query plan statistics can be enabled at the database level using the LAST_QUERY_PLAN_STATS [database scoped configuration](../../t-sql/statements/alter-database-scoped-configuration-transact-sql.md): `ALTER DATABASE SCOPED CONFIGURATION SET LAST_QUERY_PLAN_STATS = ON;`.
 
-A new *query_post_execution_plan_profile* extended event collects the equivalent of an actual execution plan based on lightweight profiling, unlike *query_post_execution_showplan* which uses standard profiling. [!INCLUDE[ssSQL17](../../includes/sssql17-md.md)] also offers this event starting with [CU14](https://support.microsoft.com/en-us/help/4490134). A sample session using the *query_post_execution_plan_profile* extended event can be configured like the example below:
+A new *query_post_execution_plan_profile* extended event collects the equivalent of an actual execution plan based on lightweight profiling, unlike *query_post_execution_showplan* which uses standard profiling. [!INCLUDE[ssSQL17](../../includes/sssql17-md.md)] also offers this event starting with CU14. A sample session using the *query_post_execution_plan_profile* extended event can be configured like the example below:
 
 ```sql
 CREATE EVENT SESSION [PerfStats_LWP_All_Plans] ON SERVER