Clarify what type pod blocks can have configuration data

doc/Language/pod.pod6

@@ -80,13 +80,15 @@ The configuration section may be extended over subsequent lines by
 starting those lines with an C<=> in the first (virtual) column followed
 by a whitespace character. (NOTE: This feature is not yet implemented.
 All configuration information currently must be provided on the same
-line as the C<=begin> marker line.)
+line as the C<=begin> marker line or C<=for name> for paragraph blocks.)
 
 =head2 Paragraph blocks
 
 Paragraph blocks begin by a C<=for> marker and end by
 the next Pod directive or the first blank line.
-The C<=for> marker is followed by the typename of the block.
+The C<=for> marker is followed by the typename of the block
+plus, optionally, any configuration data as in the delimited
+blocks described above.
 
 =begin code
 =for head1
@@ -96,7 +98,8 @@ Top Level Heading
 =head2 Abbreviated blocks
 
 Abbreviated blocks begin by an C<'='> sign, which is followed immediately by the typename of the
-block. The block ends at the next Pod directive or the
+block. All following data are part of the contents of the block, thus configuration data
+cannot be specified for an abbreviated block. The block ends at the next Pod directive or the
 first blank line.
 
 =begin code