Fixed newline again

docs/draft.html

@@ -4900,7 +4900,7 @@ <h1 data-number="4" id="conclusion"><span class="header-section-number">4</span>
 <blockquote>
 <p>github: <a href="https://github.com/cppalliance/safe-cpp">https://github.com/cppalliance/safe-cpp</a><br />
 slack: <a href="https://cpplang.slack.com/archives/C07GH9NFK0F">https://cpplang.slack.com/archives/C07GH9NFK0F</a><br />
-Circle download: <a href="https://www.circle-lang.org/">https://www.circle-lang.org/</a>
+Circle download: <a href="https://www.circle-lang.org/">https://www.circle-lang.org/</a><br />
 Working draft: <a href="https://github.com/cppalliance/safe-cpp/draft.html">https://github.com/cppalliance/safe-cpp/draft.html</a></p>
 </blockquote>
 <p>Everything in this proposal took about 18 months to design and

proposal/draft.md

@@ -2778,7 +2778,7 @@ We're co-designing the Safe C++ standard library along with the language extensi
 
 > github: [https://github.com/cppalliance/safe-cpp](https://github.com/cppalliance/safe-cpp)\
 > slack: [https://cpplang.slack.com/archives/C07GH9NFK0F](https://cpplang.slack.com/archives/C07GH9NFK0F)\
-> Circle download: [https://www.circle-lang.org/](https://www.circle-lang.org/)
+> Circle download: [https://www.circle-lang.org/](https://www.circle-lang.org/)\
 > Working draft: [https://github.com/cppalliance/safe-cpp/draft.html](https://github.com/cppalliance/safe-cpp/draft.html)
 
 Everything in this proposal took about 18 months to design and implement in Circle. With participation from industry, we could resolve the remaining design questions and in another 18 months have a language and standard library robust enough for mainstream evaluation. While Safe C++ is a large extension to the language, the cost of building new tooling is not steep. If C++ continues to go forward without a memory safety strategy, that's because institutional users are choosing not to pursue it; it's not because memory safe tooling is too expensive or difficult to build.