From b458bc9969f63a77f21f8abb241d3eaba532d7cb Mon Sep 17 00:00:00 2001 From: edent Date: Tue, 20 Feb 2018 20:35:25 +0000 Subject: [PATCH] Rephrase * Re https://github.com/w3c/html/pull/1218/files#r169206182 * Re #1215 --- sections/semantics-grouping-content.include | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/sections/semantics-grouping-content.include b/sections/semantics-grouping-content.include index 95a8fa4a84..8b16f39be4 100644 --- a/sections/semantics-grouping-content.include +++ b/sections/semantics-grouping-content.include @@ -42,10 +42,11 @@ The <{p}> element should not be used when a more specific element, such as a list, is more appropriate.
- Many elements whose typical rendering is a block, cannot be children of <{p}> elements. - When the parser finds them it automatically closes the <{p}> element - effectively inserting a </p> tag. - This includes lists, tables, heading content, most sectioning roots and sectioning content, - and <{form}>, <{fieldset}> and <{legend}> elements. + Some block elements cannot be children of <{p}> elements. + When the parser finds them, it automatically closes the <{p}> element - effectively inserting a + </p> tag. + These elements are: heading content, most sectioning roots and sectioning content, + <{form}>, <{fieldset}>, <{table}>, <{ol}>, <{ul}>, and <{legend}>.