diff --git a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/tables.mdx b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/tables.mdx
index d2890ba0ec31445..6fd9e6857e56fe1 100644
--- a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/tables.mdx
+++ b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/tables.mdx
@@ -16,12 +16,16 @@ Limit tables to three columns (or four if the information is very condensed). Ot
 
 ## Use cases
 
+The purpose of a table is to provide a scannable content experience.
+
 Use tables for:
 
 * Simple mappings of data and values
 * Categories of things with examples
 * Collections of things with different attributes
 
+Each cell within a table should not contain more than **one sentence** of content.
+
 ## Usage
 
 We use standard Markdown tables for our documentation.
@@ -52,7 +56,7 @@ When using tables:
 
 * Check whether the tables work for both desktop and mobile users.
 * Limit tables to three columns (or four if the information is very condensed).
-* Avoid long sentences or information that is so dense that it defeats the purpose of having tabular displays.
+* Avoid long sentences or information that is so dense that it defeats the purpose of having tabular displays
 
 ### Alternatives
 
@@ -60,7 +64,8 @@ If your information does not fit within the [guidelines](#guidelines), consider
 
 * Lists
 * Subsections
-* Tabs
+* [Tabs](/style-guide/components/tabs)
+* [Details](/style-guide/components/details/)
 
 ### Large tables