Update sitedocs for branch main

Author: eclipse-tycho-bot

doc/main/BndBuild.html

@@ -114,7 +114,7 @@
 <h1>BND Workspace Layout and Pomless Builds</h1>
 <p>Tycho supports building projects that use the <a href="https://bndtools.org/concepts.html" class="externalLink">BND Workspace Layout</a>.</p><section><a id="BND_Workspace_Layout"></a>
 <h2>BND Workspace Layout</h2>
-<p>A BND Workspace layout build layout usually has the following structure:</p>
+<p>A BND Workspace layout usually has the following structure:</p>
 <ul>
 
 <li><code>root folder</code> - this usually is the root of your project repository

doc/main/BuildProperties.html

@@ -122,7 +122,7 @@ <h1>Build Properties</h1>
 <li>there are other ways to achieve the desired configuration (e.g. using pom.xml)</li>
 <li>it's a missing feature</li>
 </ul>
-<p>In additional to the PDE properties, Tycho supports property expressions like <code>${project.version}</code> in <code>build.properties</code> values.
+<p>In addition to the PDE properties, Tycho supports property expressions like <code>${project.version}</code> in <code>build.properties</code> values.
 These expressions are only used in a Tycho build, not when using the Eclipse IDE incremental build.</p>
 <p>See the table below for which keys in <code>build.properties</code> defined by PDE are supported by Tycho or if not, whether there are alternatives when using Tycho.</p><section><a id="Common_Properties"></a>
 <h2>Common Properties</h2>

doc/main/Category.html

@@ -114,7 +114,7 @@
 <h1>Category</h1>
 <p>A <code>category.xml</code> file can be used to define which content is placed into a p2 repository.
 It can also specify how to display the content in the p2 installation dialog.
-For Tycho to use it, it must to be placed into the root of an project with the packaging type &#x2018;eclipse-repository&#x2019;.</p>
+For Tycho to use it, it must be placed into the root of a project with the packaging type &#x2018;eclipse-repository&#x2019;.</p>
 <p><strong>Note:</strong> The <code>eclipse-repository</code> packaging type can also be used to build Eclipse products (RCP applications). See <a href="Products.html">Building Products</a> for more information on product builds.</p>
 <p>The <code>category.xml</code> format was originally defined by the Eclipse PDE project.
 There are extensions to the format only supported by p2 and Tycho.</p>

doc/main/SBOM.html

@@ -10,7 +10,7 @@
     <meta charset="UTF-8" />
     <meta name="viewport" content="width=device-width, initial-scale=1" />
     <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0" />
-    <title>Creating SBOMs for Tycho artifacts – Tycho</title>
+    <title>Creating SBOMs for Eclipse Artifacts – Tycho</title>
     <link rel="stylesheet" href="./css/apache-maven-fluido-2.0.1.min.css" />
     <link rel="stylesheet" href="./css/site.css" />
     <link rel="stylesheet" href="./css/print.css" media="print" />
@@ -110,8 +110,8 @@
           </div>
         </header>
         <main id="bodyColumn" class="span10">
-<section><a id="Creating_SBOMs_for_Tycho_artifacts"></a>
-<h1>Creating SBOMs for Tycho artifacts</h1><section><a id="What_is_an_SBOM.3F"></a>
+<section><a id="Creating_SBOMs_for_Eclipse_Artifacts"></a>
+<h1>Creating SBOMs for Eclipse Artifacts</h1><section><a id="What_is_an_SBOM.3F"></a>
 <h2>What is an SBOM?</h2>
 <p>A Software Bill of Materials (SBOM) is a formal, machine-readable inventory of software components and dependencies, information about those components, and their hierarchical relationships. SBOMs are essential for:</p>
 <ul>

doc/main/SignProducts.html

@@ -117,7 +117,7 @@ <h1>Signing of custom Eclipse Products with Tycho</h1>
 <p>As the process of signing an executable can vary and there is no platform independent way to do this Tycho can not do it on its own and the process to do it properly requires some steps,
 so we try to give some guidance here.</p>
 <p><strong>Important note</strong> Signing the binary does not really sign your product as a whole! As Eclipse is extensible by nature it can be modified or the binary can be copied to a complete different product!</p>
-<p>As signing is usually not performed during normal development, it might be good to put the following configurations into a <code>profile</code> e.g. with the name sign-products, the current process is quite convoluted so we likey want to improve that over time to make it simpler.</p><section><a id="Step_1.3A_Move_some_of_the_executions_to_the_compile_phase"></a>
+<p>As signing is usually not performed during normal development, it might be good to put the following configurations into a <code>profile</code> e.g. with the name sign-products, the current process is quite convoluted so we likely want to improve that over time to make it simpler.</p><section><a id="Step_1.3A_Move_some_of_the_executions_to_the_compile_phase"></a>
 <h2>Step 1: Move some of the executions to the compile phase</h2>
 <p>Because we want to modify some files before they appear in the assembly repository, we first move some of the executions from the default phase into the compile phase to execute additional actions:</p>
 
@@ -142,7 +142,7 @@ <h2>Step 1: Move some of the executions to the compile phase</h2>
 &lt;/plugin&gt;
 </code></pre></section><section><a id="Step_2.3A_Expand_the_customized_product_binaries"></a>
 <h2>Step 2: Expand the customized product binaries</h2>
-<p>Maven and P2 manage artifacts as zip files so they can be transfered as a stream, because usually the signing tools are not capable to sign binaries inside a zip file we first need to extract them we use the windows binaries here as an example:</p>
+<p>Maven and P2 manage artifacts as zip files so they can be transferred as a stream, because usually the signing tools are not capable to sign binaries inside a zip file we first need to extract them we use the windows binaries here as an example:</p>
 
 <pre class="prettyprint linenums"><code class="language-xml">&lt;plugin&gt;
 	&lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;

doc/main/TargetPlatform.html

@@ -136,7 +136,7 @@ <h3>Simple target platform configuration</h3>
 
 <pre class="prettyprint linenums"><code class="language-xml">&lt;repository&gt;
    &lt;id&gt;eclipse-indigo&lt;/id&gt;
-   &lt;url&gt;http://download.eclipse.org/releases/2023-12&lt;/url&gt;
+   &lt;url&gt;https://download.eclipse.org/releases/2023-12&lt;/url&gt;
    &lt;layout&gt;p2&lt;/layout&gt;
 &lt;/repository&gt;
 </code></pre>