Fixed hyphenation mistake

cppalliance · Oct 14, 2024 · 0c4083c · 0c4083c
1 parent 0f4ee01
commit 0c4083c
Show file tree

Hide file tree

Showing 4 changed files with 6 additions and 6 deletions.
diff --git a/docs/P3444R0.html b/docs/P3444R0.html
@@ -456,8 +456,8 @@ <h1 data-number="1" id="abstract"><span class="header-section-number">1</span> A
 <ol type="1">
 <li>Explore the viability of memory safety without lifetime
 parameters.</li>
-<li>Explain the infeasibility of making legacy lvalue and rvalue
-references memory safe.</li>
+<li>Explain the infeasibility of making legacy lvalue- and
+rvalue-references memory safe.</li>
 <li>Address common objections to safety models that use lifetime
 annotations.</li>
 </ol>

diff --git a/docs/draft-lifetimes.html b/docs/draft-lifetimes.html
@@ -456,8 +456,8 @@ <h1 data-number="1" id="abstract"><span class="header-section-number">1</span> A
 <ol type="1">
 <li>Explore the viability of memory safety without lifetime
 parameters.</li>
-<li>Explain the infeasibility of making legacy lvalue and rvalue
-references memory safe.</li>
+<li>Explain the infeasibility of making legacy lvalue- and
+rvalue-references memory safe.</li>
 <li>Address common objections to safety models that use lifetime
 annotations.</li>
 </ol>

diff --git a/lifetimes/P3444R0.md b/lifetimes/P3444R0.md
@@ -14,7 +14,7 @@ toc: false
 This proposal describes the implementation of a memory-safe reference type that does not use lifetime annotations. The goal of the proposal is to:
 
 1. Explore the viability of memory safety without lifetime parameters.
-2. Explain the infeasibility of making legacy lvalue and rvalue references memory safe.
+2. Explain the infeasibility of making legacy lvalue- and rvalue-references memory safe.
 3. Address common objections to safety models that use lifetime annotations.
 
 # Safe references

diff --git a/lifetimes/draft-lifetimes.md b/lifetimes/draft-lifetimes.md
@@ -14,7 +14,7 @@ toc: false
 This proposal describes the implementation of a memory-safe reference type that does not use lifetime annotations. The goal of the proposal is to:
 
 1. Explore the viability of memory safety without lifetime parameters.
-2. Explain the infeasibility of making legacy lvalue and rvalue references memory safe.
+2. Explain the infeasibility of making legacy lvalue- and rvalue-references memory safe.
 3. Address common objections to safety models that use lifetime annotations.
 
 # Safe references