Put the P and D version in sync

cppalliance · Oct 14, 2024 · 5bee7ea · 5bee7ea
1 parent 442225f
commit 5bee7ea
Show file tree

Hide file tree

Showing 4 changed files with 301 additions and 235 deletions.
diff --git a/docs/P3444R0.html b/docs/P3444R0.html
@@ -5,7 +5,7 @@
   <meta name="generator" content="mpark/wg21" />
   <meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
   <meta name="dcterms.date" content="2024-10-15" />
-  <title>Memory safety without lifetime parameters</title>
+  <title>Memory Safety without Lifetime Parameters</title>
   <style>
       code{white-space: pre-wrap;}
       span.smallcaps{font-variant: small-caps;}
@@ -419,8 +419,8 @@
 <body>
 <div class="wrapper">
 <header id="title-block-header">
-<h1 class="title" style="text-align:center">Memory safety without
-lifetime parameters</h1>
+<h1 class="title" style="text-align:center">Memory Safety without
+Lifetime Parameters</h1>
 <table style="border:none;float:right">
   <tr>
     <td>Document #:</td>
@@ -1262,7 +1262,7 @@ <h1 data-number="5" id="lifetime-parameters"><span class="header-section-number"
 users that a garbage collection can’t, such as variables on the stack.
 Do we want more expressive references at the cost of annotations, or do
 we want to get rid of lifetime parameters to make a simpler language?
-Those are opposite goals.</li>
+Those are opposing goals.</li>
 <li><strong>Borrow checking with lifetimes is too different from normal
 C++.</strong> Borrow checking is the safety technology most similar to
 current C++ practice. This model replaces unchecked references with