htdocs: correct spelling and use https in examples

  Revised version of this patch after review.

ChangeLog:

	htdocs: correct spelling and use https in examples.



From 52d413bce86827f2add424e78321b509661f6f59 Mon Sep 17 00:00:00 2001
From: Jonathan Grant <jg@jguk.org>
Date: Wed, 6 Dec 2023 22:27:29 +0000
Subject: [PATCH] htdocs: correct spelling and use https in examples

Signed-off-by: Jonathan Grant <jg@jguk.org>
---
 htdocs/bugs/management.html               | 2 +-
 htdocs/codingrationale.html               | 2 +-
 htdocs/contribute.html                    | 6 +++---
 htdocs/gcc-14/changes.html                | 2 +-
 htdocs/gccmission.html                    | 2 +-
 htdocs/git.html                           | 7 +++----
 htdocs/projects/cfg.html                  | 2 +-
 htdocs/projects/cli.html                  | 2 +-
 htdocs/projects/cxx-reflection/index.html | 2 +-
 htdocs/projects/optimize.html             | 6 +++---
 htdocs/projects/tree-profiling.html       | 2 +-
 htdocs/testing/index.html                 | 2 +-
 12 files changed, 18 insertions(+), 19 deletions(-)
  

Ping

Thanks, Jonny


On 06/12/2023 22:33, Jonny Grant wrote:
> Revised version of this patch after review.
> 
> ChangeLog:
> 
> 	htdocs: correct spelling and use https in examples.
> 
> 
> 
>>From 52d413bce86827f2add424e78321b509661f6f59 Mon Sep 17 00:00:00 2001
> From: Jonathan Grant <jg@jguk.org>
> Date: Wed, 6 Dec 2023 22:27:29 +0000
> Subject: [PATCH] htdocs: correct spelling and use https in examples
> 
> Signed-off-by: Jonathan Grant <jg@jguk.org>
> ---
>  htdocs/bugs/management.html               | 2 +-
>  htdocs/codingrationale.html               | 2 +-
>  htdocs/contribute.html                    | 6 +++---
>  htdocs/gcc-14/changes.html                | 2 +-
>  htdocs/gccmission.html                    | 2 +-
>  htdocs/git.html                           | 7 +++----
>  htdocs/projects/cfg.html                  | 2 +-
>  htdocs/projects/cli.html                  | 2 +-
>  htdocs/projects/cxx-reflection/index.html | 2 +-
>  htdocs/projects/optimize.html             | 6 +++---
>  htdocs/projects/tree-profiling.html       | 2 +-
>  htdocs/testing/index.html                 | 2 +-
>  12 files changed, 18 insertions(+), 19 deletions(-)
> 
> diff --git a/htdocs/bugs/management.html b/htdocs/bugs/management.html
> index 28dfa76a..b2bb740e 100644
> --- a/htdocs/bugs/management.html
> +++ b/htdocs/bugs/management.html
> @@ -64,7 +64,7 @@ perspective, these are the relevant ones and what their values mean:</p>
>  The status and resolution fields define and track the life cycle of a
>  bug.  In addition to their <a
>  href="https://gcc.gnu.org/bugzilla/page.cgi?id=fields.html">regular
> -descriptions</a>, we also use two adition status values:
> +descriptions</a>, we also use two additional status values:
>  
>  <dl>
>  
> diff --git a/htdocs/codingrationale.html b/htdocs/codingrationale.html
> index 6cc76885..c51c9da4 100644
> --- a/htdocs/codingrationale.html
> +++ b/htdocs/codingrationale.html
> @@ -155,7 +155,7 @@ Wide use of implicit conversion can cause some very surprising results.
>  
>  <p>
>  C++03 has no explicit conversion operators,
> -and hence using them cannot avoid suprises.
> +and hence using them cannot avoid surprises.
>  Wait for C++11.
>  </p>
>  
> diff --git a/htdocs/contribute.html b/htdocs/contribute.html
> index 7c1ae323..152675fa 100644
> --- a/htdocs/contribute.html
> +++ b/htdocs/contribute.html
> @@ -299,7 +299,7 @@ followed by a colon.  For example,</p>
>  </ul>
>  
>  <p>Some large components may be subdivided into sub-components.  If
> -the subcomponent name is not disctinct in its own right, you can use the
> +the subcomponent name is not distinct in its own right, you can use the
>  form <i>component/sub-component:</i>.</p>
>  
>  <h4>Series identifier</h4>
> @@ -329,7 +329,7 @@ the commit message so that Bugzilla will correctly notice the
>  commit.  If your patch relates to two bugs, then write
>  <code>[PR<i>nnnnn</i>, PR<i>mmmmm</i>]</code>.  For multiple
>  bugs, just cite the most relevant one in the summary and use an
> -elipsis instead of the second, or subsequent PR numbers; list all the
> +ellipsis instead of the second, or subsequent PR numbers; list all the
>  related PRs in the body of the commit message in the normal way.</p>
>  
>  <p>It is not necessary to cite bugs that are closed as duplicates of
> @@ -354,7 +354,7 @@ together.</p>
>  <p>If you submit a new version of a patch series, then you should
>  start a new email thread (don't reply to the original patch series).
>  This avoids email threads becoming confused between discussions of the
> -first and subsequent revisions of the patch set.  Your cover leter
> +first and subsequent revisions of the patch set.  Your cover letter
>  (0/<i>nnn</i>) should explain clearly what has been changed between
>  the two patch series.  Also state if some of the patches are unchanged
>  between revisions; this saves maintainers having to re-review the
> diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
> index 5a453437..bd51ecb4 100644
> --- a/htdocs/gcc-14/changes.html
> +++ b/htdocs/gcc-14/changes.html
> @@ -34,7 +34,7 @@ a work-in-progress.</p>
>        another structure, is deprecated. Refer to
>        <a href="https://gcc.gnu.org/onlinedocs/gcc/Zero-Length.html">
>        Zero Length Arrays</a>.
> -      Any code relying on this extension should be modifed to ensure that
> +      Any code relying on this extension should be modified to ensure that
>        C99 flexible array members only end up at the ends of structures.
>        Please use the warning option
>        <a href="https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html#index-Wflex-array-member-not-at-end"><code>-Wflex-array-member-not-at-end</code></a> to
> diff --git a/htdocs/gccmission.html b/htdocs/gccmission.html
> index 58a12755..1124fe9f 100644
> --- a/htdocs/gccmission.html
> +++ b/htdocs/gccmission.html
> @@ -55,7 +55,7 @@ GCC.</p>
>   <li>Patches will be considered equally based on their
>       technical merits.</li>
>   <li>All individuals and companies are welcome to contribute
> -     as long as they accept the groundrules.</li>
> +     as long as they accept the ground rules.</li>
>   </ul></li>
>  <li>Open mailing lists.</li>
>  <li>Developer friendly tools and procedures (i.e. [version control], multiple
> diff --git a/htdocs/git.html b/htdocs/git.html
> index 22c0eec1..ed4607ef 100644
> --- a/htdocs/git.html
> +++ b/htdocs/git.html
> @@ -27,7 +27,6 @@ Git history online</a>.</p>
>  <p>(Our <a href="about.html#git">web pages are managed via Git in a
>  separate repository</a>.)</p>
>  
> -
>  <h2>Using the Git repository</h2>
>  
>  <p>Assuming you have
> @@ -35,7 +34,7 @@ separate repository</a>.)</p>
>  check out the GCC sources using the following command:</p>
>  
>  <blockquote><p>
> -<code>git clone git://gcc.gnu.org/git/gcc.git SomeLocalDir</code>
> +<code>git clone https://gcc.gnu.org/git/gcc.git SomeLocalDir</code>
>  </p></blockquote>
>  
>  <p>If you are behind a firewall that does not allow the git protocol
> @@ -44,7 +43,7 @@ through, you can replace <code>git://</code> with <code>https://</code>.
>  <p>If there is another local repository accessible you can avoid
>  re-downloading everything by using <code>--reference</code>, e.g.</p>
>  
> -<blockquote><code>git clone --reference original-gcc --dissociate ssh://gcc.gnu.org/git/gcc.git new-gcc</code></blockquote>
> +<blockquote><code>git clone --reference original-gcc --dissociate https://gcc.gnu.org/git/gcc.git new-gcc</code></blockquote>
>  
>  <p>But if you own this other copy, you probably want to use
>  separate <a href="#worktrees">worktrees</a> instead of multiple clones.
> @@ -236,7 +235,7 @@ additional branches can also be fetched if necessary.</p>
>  </ul>
>  
>  <p>You can download any of the additional branches by adding a suitable
> -fetch specification to your local copy of the git repostiory.  For
> +fetch specification to your local copy of the git repository.  For
>  example, if your remote is called 'origin' (the default with git
>  clone) you can add the 'dead' development branches by running:</p>
>  
> diff --git a/htdocs/projects/cfg.html b/htdocs/projects/cfg.html
> index b1ee1f34..b695766e 100644
> --- a/htdocs/projects/cfg.html
> +++ b/htdocs/projects/cfg.html
> @@ -83,7 +83,7 @@ to peel more than one iteration.</p>
>  
>  <p>The current loop optimizer uses information passed by the front end
>  to discover loop constructs to simplify flow analysis.
> -It is difficult to keep the information up-to-date and nowday
> +It is difficult to keep the information up-to-date and nowadays
>  it is easy to implement the loop discovery code on CFG.
>  </p>
>  
> diff --git a/htdocs/projects/cli.html b/htdocs/projects/cli.html
> index 394832b6..26bf5274 100644
> --- a/htdocs/projects/cli.html
> +++ b/htdocs/projects/cli.html
> @@ -152,7 +152,7 @@ front end and the CLI binutils (both Mono based and DotGnu based) .
>  
>  <h2 id="internals">The CLI back end</h2>
>  <p>
> -Unlike a typical GCC back end, the CLI backnend stops the compilation flow
> +Unlike a typical GCC back end, the CLI backend stops the compilation flow
>  at the end of the middle-end passes and, without going through any RTL
>  pass, it emits CIL bytecode from GIMPLE representation.
>  As a matter of fact, RTL is not a convenient representation to emit
> diff --git a/htdocs/projects/cxx-reflection/index.html b/htdocs/projects/cxx-reflection/index.html
> index 2aefd708..709e012f 100644
> --- a/htdocs/projects/cxx-reflection/index.html
> +++ b/htdocs/projects/cxx-reflection/index.html
> @@ -53,7 +53,7 @@ complete, you should:</p>
>  <p>Patches that break default bootstraps will be removed (if a
>  fix is not immediately obvious).</p>
>  
> -<p>When submitting patches that implement new fonctionalities, please
> +<p>When submitting patches that implement new functionalities, please
>  include a reference to the paper and/or book where you are getting the
>  complete syntactic and semantic specifications from.  If it's your own
>  research work, include a Technical Report, Thesis or Paper reference
> diff --git a/htdocs/projects/optimize.html b/htdocs/projects/optimize.html
> index 26262637..6354c726 100644
> --- a/htdocs/projects/optimize.html
> +++ b/htdocs/projects/optimize.html
> @@ -220,7 +220,7 @@ implemented by processor specific instructions.  These transformations
>  are better performed in GCC, both to reduce the overhead of macro
>  expansion and to take advantage of the functions attributes, for
>  example to avoid a second call to a pure function altogether.  The
> -use of these macros tend to cause huge blowup in the size of preprocessed
> +use of these macros tend to cause huge increase in the size of preprocessed
>  source if nested; for example, each nested call to <code>strcpy</code>
>  expands the source 20-fold, with four nested calls having an expansion
>  ten megabytes in size.  GCC then consumes a huge amount of memory
> @@ -290,8 +290,8 @@ target.</p>
>  </ul>
>  
>  <p><strong>Note:</strong> If an issue listed in a target specific issues
> -page, but it clearly is a target indepentent issue, please move it to
> -a page discussing target indepentent issues</p>
> +page, but it clearly is a target independent issue, please move it to
> +a page discussing target independent issues</p>
>  
>  </body>
>  </html>
> diff --git a/htdocs/projects/tree-profiling.html b/htdocs/projects/tree-profiling.html
> index 4aecc34c..31553061 100644
> --- a/htdocs/projects/tree-profiling.html
> +++ b/htdocs/projects/tree-profiling.html
> @@ -7,7 +7,7 @@
>  <link rel="stylesheet" type="text/css" href="https://gcc.gnu.org/gcc.css">
>  </head>
>  <body>
> -<h1>Improving GCC's Interprocedural Optimizaion Infrastructure</h1>
> +<h1>Improving GCC's Interprocedural Optimization Infrastructure</h1>
>  
>  <p>This page describes ongoing work to improve GCC's infrastructure
>  for tree-based interprocedural optimizers. The work is done on a
> diff --git a/htdocs/testing/index.html b/htdocs/testing/index.html
> index 012ac287..f0c75837 100644
> --- a/htdocs/testing/index.html
> +++ b/htdocs/testing/index.html
> @@ -38,7 +38,7 @@ the testsuite directories.</p>
>        <a href="https://gcc.gnu.org/ml/gcc-testresults/">gcc-testresults
>        mailing list</a>.</li>
>  
> -  <li>Jan-Benedict Glaw is runing a
> +  <li>Jan-Benedict Glaw is running a
>        <a href="http://toolchain.lug-owl.de/buildbot/">build robot</a> that
>        tries to build various cross-targets (stage1 only) on some machines.</li>
>  </ul>