docs: correct description of multiline patterns usage based on #1353 (#…

…1380)

docs/rules/configurable-rules.md

@@ -493,10 +493,9 @@ rules:
       notPattern: /^The/
 ```
 
-Take care using `notPattern` with multiline Markdown values such as
-`description` fields. These may end with a newline rather than the character
-you expect. Use the trimmed notations (`|-` or `>-`) or take account of this in
-your pattern.
+Take care using `notPattern` with multiline Markdown values such as `description` fields.
+These may end with a newline or a space rather than the character you expect.
+Use the [double-quoted style](https://yaml.org/spec/1.2.2/#731-double-quoted-style) or take account of this in your pattern.
 
 ### `pattern` example
 
@@ -512,9 +511,9 @@ rules:
       pattern: /test/
 ```
 
-Take care using `pattern` with multiline Markdown values such as `description`
-fields. These may end with a newline rather than the character you expect. Use
-the trimmed notations (`|-` or `>-`) or take account of this in your pattern.
+Take care using `pattern` with multiline Markdown values such as `description` fields.
+These may end with a newline or a space rather than the character you expect.
+Use the [double-quoted style](https://yaml.org/spec/1.2.2/#731-double-quoted-style) or take account of this in your pattern.
 
 ### `ref` example