Remove 'repeatable' isolation level from multinode docs (github#361)

Co-authored-by: Jacob Prall <prall.jacob@gmail.com>
jnidzwetzki · Sep 10, 2021 · aa19b24 · aa19b24
1 parent 3b26dbb
commit aa19b24
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/timescaledb/how-to-guides/multi-node-setup/required-configuration.md b/timescaledb/how-to-guides/multi-node-setup/required-configuration.md
@@ -18,7 +18,7 @@ data nodes (if not already set, `150` is recommended).
   environment.
 * For consistency, if the transaction isolation level is set to `READ COMMITTED` it is
   automatically upgraded to `REPEATABLE READ` whenever a distributed operation
-  takes place. If the isolation level is `READ COMMITTED` or `SERIALIZABLE`, it is not changed.
+  takes place. If the isolation level is `SERIALIZABLE`, it is not changed.
 
 Each of the above settings parameters can be configured for the
 instance in `postgresql.conf`, typically located in the data