diff --git a/doc/src/sgml/ref/alter_table.sgml b/doc/src/sgml/ref/alter_table.sgml
index 9b34c4fb993..0f55f81d99d 100644
--- a/doc/src/sgml/ref/alter_table.sgml
+++ b/doc/src/sgml/ref/alter_table.sgml
@@ -1,5 +1,5 @@
@@ -213,13 +213,13 @@ where action is one of:
requires superuser privileges; it should be done with caution since
of course the integrity of the constraint cannot be guaranteed if the
triggers are not executed.
- The trigger firing mechanism is also affected by the configuration
- variable . Simply ENABLEd
- triggers will fire when the replication role is origin>
- (the default) or local>. Triggers configured ENABLE REPLICA
- will only fire if the session is in replica> mode and triggers
- configured ENABLE ALWAYS will fire regardless of the current replication
- mode.
+ The trigger firing mechanism is also affected by the configuration
+ variable . Simply ENABLEd
+ triggers will fire when the replication role is origin>
+ (the default) or local>. Triggers configured ENABLE REPLICA
+ will only fire if the session is in replica> mode and triggers
+ configured ENABLE ALWAYS will fire regardless of the current replication
+ mode.
@@ -230,10 +230,10 @@ where action is one of:
These forms configure the firing of rewrite rules belonging to the table.
A disabled rule is still known to the system, but is not applied
- during query rewriting. The semantics are as for disabled/enabled
- triggers. This configuration is ignored for ON SELECT rules, which
- are always applied in order to keep views working even if the current
- session is in a non-default replication role.
+ during query rewriting. The semantics are as for disabled/enabled
+ triggers. This configuration is ignored for ON SELECT rules, which
+ are always applied in order to keep views working even if the current
+ session is in a non-default replication role.