Update documentation

_sources/building_the_project_with_dpcpp.rst

@@ -341,7 +341,7 @@ The following table provides details of CMake options and their default values:
 CMake invocation examples
 ##########################
 
-Build oneMKL with support for x86 CPU, Intel GPU, and Nvidia GPUs with tests
+Build oneMKL with support for Nvidia GPUs with tests
 disabled using the Ninja build system:
 
 .. code-block:: bash
@@ -363,7 +363,7 @@ and Intel GPU (``MKLGPU``) backends are enabled by default, but are disabled
 here. The backends for Nvidia GPUs must all be explicilty enabled. The tests are
 disabled, but the examples will still be built.
 
-Building oneMKL with support x86 CPU, Intel GPU, and AMD GPUs with tests
+Building oneMKL with support for AMD GPUs with tests
 disabled:
 
 .. code-block:: bash
@@ -401,7 +401,7 @@ GPU and Nvidia GPU with testing enabled:
 Note that this is not a supported configuration, and requires Codeplay's oneAPI
 for `AMD <https://developer.codeplay.com/products/oneapi/amd/home/>`_ and
 `Nvidia <https://developer.codeplay.com/products/oneapi/nvidia/home/>`_ GPU
-plugins. Like the above example, the MKLCPU and MKLGPU backends are enabled by
+plugins. The MKLCPU and MKLGPU backends are enabled by
 default, with backends for Nvidia GPU and AMD GPU explicitly enabled.
 ``-DTARGET_DOMAINS=dft`` causes only DFT backends to be built. If this was not
 set, the backend libraries to enable the use of BLAS, LAPACK and RNG with MKLGPU

building_the_project_with_dpcpp.html

@@ -868,7 +868,7 @@ <h2>Backends<a class="headerlink" href="#backends" title="Link to this heading">
 </section>
 <section id="cmake-invocation-examples">
 <span id="build-invocation-examples-dpcpp"></span><h2>CMake invocation examples<a class="headerlink" href="#cmake-invocation-examples" title="Link to this heading">#</a></h2>
-<p>Build oneMKL with support for x86 CPU, Intel GPU, and Nvidia GPUs with tests
+<p>Build oneMKL with support for Nvidia GPUs with tests
 disabled using the Ninja build system:</p>
 <div class="highlight-bash notranslate"><div class="highlight"><pre><span></span>cmake<span class="w"> </span><span class="nv">$ONEMKL_DIR</span><span class="w"> </span><span class="se">\</span>
 <span class="w">    </span>-GNinja<span class="w"> </span><span class="se">\</span>
@@ -887,7 +887,7 @@ <h2>Backends<a class="headerlink" href="#backends" title="Link to this heading">
 and Intel GPU (<code class="docutils literal notranslate"><span class="pre">MKLGPU</span></code>) backends are enabled by default, but are disabled
 here. The backends for Nvidia GPUs must all be explicilty enabled. The tests are
 disabled, but the examples will still be built.</p>
-<p>Building oneMKL with support x86 CPU, Intel GPU, and AMD GPUs with tests
+<p>Building oneMKL with support for AMD GPUs with tests
 disabled:</p>
 <div class="highlight-bash notranslate"><div class="highlight"><pre><span></span>cmake<span class="w"> </span><span class="nv">$ONEMKL_DIR</span><span class="w"> </span><span class="se">\</span>
 <span class="w">    </span>-DCMAKE_CXX_COMPILER<span class="o">=</span>clang++<span class="w"> </span><span class="se">\</span>
@@ -919,7 +919,7 @@ <h2>Backends<a class="headerlink" href="#backends" title="Link to this heading">
 <p>Note that this is not a supported configuration, and requires Codeplay’s oneAPI
 for <a class="reference external" href="https://developer.codeplay.com/products/oneapi/amd/home/">AMD</a> and
 <a class="reference external" href="https://developer.codeplay.com/products/oneapi/nvidia/home/">Nvidia</a> GPU
-plugins. Like the above example, the MKLCPU and MKLGPU backends are enabled by
+plugins. The MKLCPU and MKLGPU backends are enabled by
 default, with backends for Nvidia GPU and AMD GPU explicitly enabled.
 <code class="docutils literal notranslate"><span class="pre">-DTARGET_DOMAINS=dft</span></code> causes only DFT backends to be built. If this was not
 set, the backend libraries to enable the use of BLAS, LAPACK and RNG with MKLGPU