Update docs/integrations/data-ingestion/etl-tools/dbt/features-and-configurations.md

Co-authored-by: Bentsi Leviav <bentsi.leviav@clickhouse.com>

Author: koletzilla

docs/integrations/data-ingestion/etl-tools/dbt/features-and-configurations.md

@@ -123,7 +123,7 @@ be created on the connected node only).
 If a model has been created without a `cluster` setting, dbt-clickhouse will detect the situation and run all DDL/DML
 without `on cluster` clause for this model.
 
-#### Read-after-write consistency {#read-after-write-consistency}
+#### Read-after-write Consistency {#read-after-write-consistency}
 
 dbt relies on a read-after-insert consistency model. This is not compatible with ClickHouse clusters that have more than one replica if you cannot guarantee that all operations will go to the same replica. You may not encounter problems in your day-to-day usage of dbt, but there are some strategies depending on your cluster to have this guarantee in place:
 - If you are using a ClickHouse Cloud cluster, you only need to set `select_sequential_consistency: 1` in your profile's `custom_settings` property. You can find more information about this setting [here](https://clickhouse.com/docs/operations/settings/settings#select_sequential_consistency).