Update minimize_optimize_joins.md

Author: Blargian

docs/best-practices/minimize_optimize_joins.md

@@ -41,7 +41,7 @@ Follow these best practices to improve JOIN performance:
 When using dictionaries for JOINs in ClickHouse, it's important to understand that dictionaries, by design, do not allow duplicate keys. During data loading, any duplicate keys are silently deduplicated—only the last loaded value for a given key is retained. This behavior makes dictionaries ideal for one-to-one or many-to-one relationships where only the latest or authoritative value is needed. However, using a dictionary for a one-to-many or many-to-many relationship (e.g. joining roles to actors where an actor can have multiple roles) will result in silent data loss, as all but one of the matching rows will be discarded. As a result, dictionaries are not suitable for scenarios requiring full relational fidelity across multiple matches.
 :::
 
-## Choosing the right JOIN Algorithm {#choosing-the-right-join-algorithm}
+## Choosing the correct JOIN Algorithm {#choosing-the-right-join-algorithm}
 
 ClickHouse supports several JOIN algorithms that trade off between speed and memory: