diff --git a/Definition-Format-Enhancement.md.md b/Definition-Format-Enhancement.md.md
index 47cf5d7..73cfd4e 100644
--- a/Definition-Format-Enhancement.md.md
+++ b/Definition-Format-Enhancement.md.md
@@ -443,4 +443,5 @@ Enter your alternative proposals and comments in a new section (use `## Your hea
 
 ## Discussion of Goals
 
-- No. 7 single- versus multi-lines. The back ticks are horrible and will cause a storm of malice and hatred greater than the current discontent with blank lines. I see no advantage over the blank lines which work fine and do not look ugly.
\ No newline at end of file
+- No. 7 single- versus multi-lines. The back ticks are horrible and will cause a storm of malice and hatred greater than the current discontent with blank lines. I see no advantage over the blank lines which work fine and do not look ugly.
+    - +1 - Backticks used in this way are unfamiliar and therefore confusing.  Line continuations, by which I presume we mean shell style `\` (backslash) or something similar would at least be familiar though not in the context of Scala code or YAML / properties files---all of which are visually similar to the proposal and likely to provide cues to expectations.  How about using indents to indicate line continuations.  This would be in keeping with the existing structure which uses indentation to indicate that the lines that follow are all the 'continuation' of a section.
\ No newline at end of file