public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@pfeifer.com>
To: gcc-patches@gcc.gnu.org
Subject: [committed] wwwdocs: gcc-12: Spelling fixes
Date: Sun, 25 Dec 2022 12:51:39 +0100 (CET)	[thread overview]
Message-ID: <20221225115141.A09EC33E8A@hamza.pair.com> (raw)

A case of British to American English, too, for consistency.

Gerald
---
 htdocs/gcc-12/changes.html | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
index 30fa4d6e..b3775f82 100644
--- a/htdocs/gcc-12/changes.html
+++ b/htdocs/gcc-12/changes.html
@@ -252,7 +252,7 @@ You may also want to check out our
         will "slide" to the correct lower bound of the subtype.</li>
     </ul>
     </li>
-    <li>Generalized <code>Object.Operand</code> notation. The follwing
+    <li>Generalized <code>Object.Operand</code> notation. The following
       code is now valid <code>V.Add_Element(42);</code>,
       with <code>V</code> being a vector, for example.</li>
     <li>Additional <code>when</code> constructs. Keywords
@@ -551,13 +551,13 @@ function Multiply (S1, S2 : Sign) return Sign is
       <li><code>-fcheck=</code>, enables or disables the code generation of
 	specific run-time contract checks.
       </li>
-      <li><code>-fcheckaction=</code>, controls the run-time behaviour on an
+      <li><code>-fcheckaction=</code>, controls the run-time behavior on an
 	assert, array bounds check, or final switch contract failure. The
 	default is <code>-fcheckaction=throw</code>.
       </li>
       <li><code>-fdump-c++-spec=</code>, dumps all compiled
 	<code>extern(C++)</code> declarations as C++ code to the given file.
-	The supplimentary option <code>-fdump-c++-spec-verbose</code> turns on
+	The supplementary option <code>-fdump-c++-spec-verbose</code> turns on
 	emission of comments for ignored declarations in the generated spec.
       </li>
       <li><code>-fextern-std=</code>, controls which C++ standard
@@ -611,7 +611,7 @@ function Multiply (S1, S2 : Sign) return Sign is
     option now selects the IEEE 128-bit floating point format
     for <code>REAL(KIND=16)</code>.
     <code>R16_IBM</code> and <code>R16_IEEE</code> have been added to the
-    <code>-fconvert</code> option, the <code>CONVERT</code> specifyer of
+    <code>-fconvert</code> option, the <code>CONVERT</code> specifier of
     the <code>OPEN</code> statement and the <code>GFORTRAN_CONVERT_UNIT</code>
     environment variable.
   </li>
@@ -625,7 +625,7 @@ function Multiply (S1, S2 : Sign) return Sign is
 <ul>
   <li>The libgccjit API gained 30 new entry points:
     <ul>
-      <li>17 new "reflection" entrypoints for querying functions and types (<a href="https://gcc.gnu.org/onlinedocs/gcc-12.1.0/jit/topics/compatibility.html#libgccjit-abi-16"><code>LIBGCCJIT_ABI_16</code></a>)
+      <li>17 new "reflection" entry points for querying functions and types (<a href="https://gcc.gnu.org/onlinedocs/gcc-12.1.0/jit/topics/compatibility.html#libgccjit-abi-16"><code>LIBGCCJIT_ABI_16</code></a>)
       </li>
       <li>
 	<a href="https://gcc.gnu.org/onlinedocs/gcc-12.1.0/jit/topics/expressions.html#c.gcc_jit_lvalue_set_tls_model"><code>gcc_jit_lvalue_set_tls_model</code></a>
@@ -638,7 +638,7 @@ function Multiply (S1, S2 : Sign) return Sign is
 	<a href="https://gcc.gnu.org/onlinedocs/gcc-12.1.0/gcc/Common-Variable-Attributes.html#index-section-variable-attribute"><code>__attribute__((section(".section")))</code></a>
 	(<a href="https://gcc.gnu.org/onlinedocs/gcc-12.1.0/jit/topics/compatibility.html#libgccjit-abi-18"><code>LIBGCCJIT_ABI_18</code></a>)
       </li>
-      <li>4 new entrypoints for initializing global variables and creating
+      <li>4 new entry points for initializing global variables and creating
 	constructors for rvalues
 	(<a href="https://gcc.gnu.org/onlinedocs/gcc-12.1.0/jit/topics/compatibility.html#libgccjit-abi-19"><code>LIBGCCJIT_ABI_19</code></a>)
       </li>
@@ -659,7 +659,7 @@ function Multiply (S1, S2 : Sign) return Sign is
 	(<a href="https://gcc.gnu.org/onlinedocs/gcc-12.1.0/jit/topics/compatibility.html#libgccjit-abi-23"><code>LIBGCCJIT_ABI_23</code></a>)
       </li>
       <li>
-	2 new entrypoints for setting the alignment of a variable
+	2 new entry points for setting the alignment of a variable
 	(<a href="https://gcc.gnu.org/onlinedocs/gcc-12.1.0/jit/topics/compatibility.html#libgccjit-abi-24"><code>LIBGCCJIT_ABI_24</code></a>)
       </li>
     </ul>
@@ -984,7 +984,7 @@ function Multiply (S1, S2 : Sign) return Sign is
       "tainted" values, for consistency with the new warnings.
     </p>
     <p>A new <a href="https://gcc.gnu.org/onlinedocs/gcc-12.1.0/gcc/Common-Function-Attributes.html#index-tainted_005fargs-function-attribute"><code>__attribute__ ((tainted_args))</code></a> has been
-      added to the C and C++ frontends, usable on functions, and on
+      added to the C and C++ front ends, usable on functions, and on
       function pointer callback fields in structs.  The analyzer's taint
       mode will treat all parameters and buffers pointed to by parameters
       of such functions as being attacker-controlled, such as for
-- 
2.38.1

                 reply	other threads:[~2022-12-25 11:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20221225115141.A09EC33E8A@hamza.pair.com \
    --to=gerald@pfeifer.com \
    --cc=gcc-patches@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).