diff --git a/modules/ROOT/pages/edifact-receive-read-settings.adoc b/modules/ROOT/pages/edifact-receive-read-settings.adoc
index 92ca776c..198ab43a 100644
--- a/modules/ROOT/pages/edifact-receive-read-settings.adoc
+++ b/modules/ROOT/pages/edifact-receive-read-settings.adoc
@@ -67,6 +67,7 @@ a|* If selected, Partner Manager rejects a message that contains segments that r
 |Enforce code set validations
 a|* If selected, Partner Manager enforces EDIFACT code set validations, as defined in the EDIFACT schemas.
 * If not selected, Partner Manager accepts the message.
+|Disabled
 |===
 
 If a message does not meet an enabled rule, Partner Manager rejects it.
diff --git a/modules/ROOT/pages/message-type-send-to-partners.adoc b/modules/ROOT/pages/message-type-send-to-partners.adoc
index 3cb678b9..eb4a30ed 100644
--- a/modules/ROOT/pages/message-type-send-to-partners.adoc
+++ b/modules/ROOT/pages/message-type-send-to-partners.adoc
@@ -31,7 +31,7 @@ Enables you to import a customized xref:connectors::x12-edi/x12-edi-schema-langu
 +
 When using a customized EDI schema, you can assign a custom name to the message type definition, for example, `EDIFACT-d97a-ORDERS-<PartnerName>`.
 | Use standard EDIFACT- <version>| Yes
-|Name |Message type name that Partner Manager automatically generates from the schema filename. You can modify this name. | Yes
+|Name |Message type name that Partner Manager automatically generates from the schema filename. You can modify this name. | | Yes
 |===
 
 == JSON or XML
@@ -46,7 +46,7 @@ If you process cXML messages with <DOCTYPE> tags, you must set the `minMuleVersi
 |Usage | Message usage. Allowed value is `Send to partners`. | | Yes
 |Format | Format of the message. Allowed value is `JSON` or `XML`. | |Yes
 |Schema | Imported JSON or XSD schema file for the message type. | |No
-|Name | Name of the new message type |Yes
+|Name | Name of the new message type | |Yes
 |===
 
 == X12
@@ -70,7 +70,7 @@ Enables you to import a customized xref:connectors::x12-edi/x12-edi-schema-langu
 +
 When using the customized EDI schema, you can assign a custom name to the message type definition, for example, `X12-7050-204-PartnerName`.
 | Use standard X12-<version> |Yes
-| Message type name that Partner Manager automatically generates from the schema filename. You can modify this name.  | |Yes
+|Name | Message type name that Partner Manager automatically generates from the schema filename. You can modify this name.  | |Yes
 |===
 
 For an example that shows how to customize an X12 schema, see https://www.mulesoft.com/exchange/works.integration/b2b-x12-custom-schema-example[Customize EDI X12 Schema for B2B Integrations] in Anypoint Exchange.
diff --git a/modules/ROOT/pages/x12-receive-read-settings.adoc b/modules/ROOT/pages/x12-receive-read-settings.adoc
index 3995f068..1af4d8d5 100644
--- a/modules/ROOT/pages/x12-receive-read-settings.adoc
+++ b/modules/ROOT/pages/x12-receive-read-settings.adoc
@@ -34,7 +34,7 @@ When unchecked, the AK3 segment of the generated 997 functional acknowledgment d
 |Enabled
 
 |Report segment details
-||If selected, the details of segment errors are included in the functional acknowledgements generated (997) •
+|If selected, the details of segment errors are included in the functional acknowledgements generated (997).
 
 |Enabled