Improved wording in #302

emailmonday · Feb 18, 2024 · fcd8d5b · fcd8d5b
1 parent 29dee48
commit fcd8d5b
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/docs/content/best-practices.md b/docs/content/best-practices.md
@@ -27,7 +27,7 @@ That means:
 
 1. **Use `<table border="0" cellpadding="0" cellspacing="0" role="presentation">` when creating new tables.** This negates any unwanted spacing and borders and tells screen readers to skip over the table’s tags and move straight into the content.
 2. **When in doubt, nest another table.** For finer control of your HTML, nest tables when building emails.
-3. **Don't rely on CSS inheritance.** Some versions of Windows Outlook reset CSS properties `font-family`, `font-size`, `font-weight`, `line-height`, `color` from parent elements from `<body>` when nesting tables.
+3. **Don’t rely on CSS inheritance.** Some versions of Windows Outlook reset CSS properties like `font-family`, `font-size`, `font-weight`, `line-height`, and `color` that should be inherited in parent elements from `<body>` when nesting tables. It’s also best to place styles in the `<td>` tag (rather than `<table>` or `<tr>`).
 4. **Use padding for spacing in table cells.** Margins aren’t fully supported on tables and container elements.
 5. **Use margin for typography.** Margins *are* fully supported for headlines, paragraphs, and lists.
 6. **Use `align` for layout instead of `float`, `grid`, or `flexbox`.** Floats aren’t supported in Outlook and email clients don’t have good support for modern CSS layout properties in general.