Update

Author: github-actions

Build-options.html

@@ -375,7 +375,7 @@ <h2 id="using-build-options">Using build options</h2>
 a colon:</p>
 <pre><code class="language-console">$ meson configure -Dsubproject:option=newvalue
 </code></pre>
-<p><strong>NOTE:</strong> If you cannot call <code>meson configure</code> you likely have a old
+<p><strong>NOTE:</strong> If you cannot call <code>meson configure</code> you likely have an old
 version of Meson. In that case you can call <code>mesonconf</code> instead, but
 that is deprecated in newer versions</p>
 <h2 id="yielding-to-superproject-option">Yielding to superproject option</h2>

Builtin-options.html

@@ -359,7 +359,7 @@ <h3 id="core-options">Core options</h3>
 <tr>
 <td> genvslite {vs2022}</td>
 <td> vs2022</td>
-<td> Setup multi-builtype ninja build directories and Visual Studio solution</td>
+<td> Setup multi-buildtype ninja build directories and Visual Studio solution</td>
 <td> no</td>
 <td> no</td>
 </tr>
@@ -520,7 +520,7 @@ <h4 id="details-for-genvslite">Details for <code>genvslite</code>
 <p>Setup multiple buildtype-suffixed, ninja-backend build directories (e.g.
 [builddir]_[debug/release/etc.]) and generate [builddir]_vs containing a Visual
 Studio solution with multiple configurations that invoke a meson compile of the
-setup build directories, as appropriate for the current configuration (builtype).</p>
+setup build directories, as appropriate for the current configuration (buildtype).</p>
 <p>This has the effect of a simple setup macro of multiple 'meson setup ...'
 invocations with a set of different buildtype values.  E.g.
 <code>meson setup ... --genvslite vs2022 somebuilddir</code> does the following -</p>
@@ -580,7 +580,7 @@ <h4 id="details-for-buildtype">Details for <code>buildtype</code>
 <p>All other combinations of <code>debug</code> and <code>optimization</code> set <code>buildtype</code> to <code>'custom'</code>.</p>
 <h4 id="details-for-warning_level">Details for <code>warning_level</code>
 </h4>
-<p>Exact flags per warning level is compiler specific, but there is an approximative
+<p>Exact flags per warning level is compiler specific, but there is an approximate
 table for most common compilers.</p>
 <table>
 <thead>

FAQ.html

@@ -424,7 +424,7 @@ <h2 id="does-wrap-download-sources-behind-my-back">Does wrap download sources be
 or they are not called (due to e.g. <code>if/else</code>) then nothing is
 downloaded.</p>
 <p>If this is not sufficient for you, starting from release 0.40.0 Meson
-has a option called <code>wrap-mode</code> which can be used to disable wrap
+has an option called <code>wrap-mode</code> which can be used to disable wrap
 downloads altogether with <code>--wrap-mode=nodownload</code>. You can also
 disable dependency fallbacks altogether with <code>--wrap-mode=nofallback</code>,
 which also implies the <code>nodownload</code> option.</p>

IDE-integration.html

@@ -217,7 +217,7 @@ <h1 id="ide-integration">IDE integration</h1>
 this problem, Meson provides an API that makes it easy for any IDE or
 build tools to integrate Meson builds and provide an experience
 comparable to a solution native to the IDE.</p>
-<p>All the resources required for such a IDE integration can be found in
+<p>All the resources required for such an IDE integration can be found in
 the <code>meson-info</code> directory in the build directory.</p>
 <p>The first thing to do when setting up a Meson project in an IDE is to
 select the source and build directories. For this example we assume

Include-directories.html

@@ -215,7 +215,7 @@ <h1 id="include-directories">Include directories</h1>
 <p>Most <code>C</code>/<code>C++</code> projects have headers in different directories than
 sources. Thus you need to specify include directories. Let's assume
 that we are at some subdirectory and wish to add its <code>include</code>
-subdirectory to some target's search path. To create a include
+subdirectory to some target's search path. To create an include
 directory object we do this:</p>
 <pre><code class="language-meson">incdir = include_directories('include')
 </code></pre>

Qt6-module.html

@@ -294,7 +294,7 @@ <h2 id="compile_moc">compile_moc</h2>
 it generates a file <code>{target private directory}/subdir/one.out</code> when <code>true</code>,
 and <code>{target private directory}/one.out</code> when <code>false</code> (default).</li>
 <li>
-<code>output_json</code> bool: <em>New in 1.7.0</em>. If <code>true</code>, generates additionnaly a
+<code>output_json</code> bool: <em>New in 1.7.0</em>. If <code>true</code>, generates additionally a
 JSON representation which may be used by external tools such as qmltyperegistrar</li>
 </ul>
 <h2 id="preprocess">preprocess</h2>

Unit-tests.html

@@ -411,7 +411,7 @@ <h3 id="other-test-options">Other test options</h3>
 <p>For further information see the command line help of Meson by running
 <code>meson test -h</code>.</p>
 <h2 id="legacy-notes">Legacy notes</h2>
-<p>If <code>meson test</code> does not work for you, you likely have a old version
+<p>If <code>meson test</code> does not work for you, you likely have an old version
 of Meson. In that case you should call <code>mesontest</code> instead. If
 <code>mesontest</code> doesn't work either you have a very old version prior to
 0.37.0 and should upgrade.</p>

assets/js/search/additionally

@@ -0,0 +1 @@
+urls_downloaded_cb({"token":"approximate","urls":[{"url":"Builtin-options.html#details-for-warning_level","node_type":"p","page":"Built-in options","sections":["Built-in options","Universal options","Core options","Details for warning_level\n"],"context":{"gi-language":["default"]}}]});