Merge pull request #50838 from AzureMentor/patch-26

Should be "perform", not "performance"

Author: ktoliver

articles/synapse-analytics/sql-data-warehouse/sql-data-warehouse-tables-index.md

@@ -65,7 +65,7 @@ WITH ( HEAP );
 
 ## Clustered and nonclustered indexes
 
-Clustered indexes may outperform clustered columnstore tables when a single row needs to be quickly retrieved. For queries where a single or very few row lookup is required to performance with extreme speed, consider a cluster index or nonclustered secondary index. The disadvantage to using a clustered index is that only queries that benefit are the ones that use a highly selective filter on the clustered index column. To improve filter on other columns a nonclustered index can be added to other columns. However, each index which is added to a table adds both space and processing time to loads.
+Clustered indexes may outperform clustered columnstore tables when a single row needs to be quickly retrieved. For queries where a single or very few row lookup is required to perform with extreme speed, consider a cluster index or nonclustered secondary index. The disadvantage to using a clustered index is that only queries that benefit are the ones that use a highly selective filter on the clustered index column. To improve filter on other columns a nonclustered index can be added to other columns. However, each index which is added to a table adds both space and processing time to loads.
 
 To create a clustered index table, simply specify CLUSTERED INDEX in the WITH clause: