Docs for pull request 2304

Author: github-actions[doc-deploy-bot]

pulls/2304/_sources/api_reference/dpctl/filter_selector_string.rst.txt

@@ -24,7 +24,7 @@ least one component.
 ``Backend`` specifies the desired backend of targeted devices, while
 ``DeviceType`` specifies the type of targeted devices.
 ``RelativeDeviceNumber`` refers to the number of the device that matches
-any other given requirements, starting from `0` to marking the
+any other given requirements, starting from 0 to marking the
 "first device that matches the requirements".
 
 Attempting to use a non-conforming string in places where filter selector

pulls/2304/_sources/api_reference/dpctl_cmake.rst.txt

@@ -3,7 +3,7 @@
 CMake support
 =============
 
-:py:mod:`dpctl` comes with the configuration file `dpctl-config.cmake` which is installed
+:py:mod:`dpctl` comes with the configuration file :file:`dpctl-config.cmake` which is installed
 on the `standard search path CMake uses to search for packages <cmake_find_package_search_paths_>`_.
 
 To build your extension that leverages :py:mod:`dpctl`, include the following line in your CMake script:

pulls/2304/_sources/beginners_guides/installation.rst.txt

@@ -211,7 +211,7 @@ AMD build
 
     python scripts/build_locally.py --verbose --target-hip=<arch>
 
-Note that the `oneAPI for AMD GPUs` plugin requires the architecture be specified and only
+Note that the oneAPI for AMD GPUs plugin requires the architecture be specified and only
 one architecture can be specified at a time.
 
 To determine the architecture code (``<arch>``) for your AMD GPU, run:

pulls/2304/_sources/beginners_guides/managing_devices.rst.txt

@@ -310,7 +310,7 @@ For Intel GPU devices, additional architectural information can be access with :
 
     In [2]: d_gpu = dpctl.SyclDevice()
 
-    # Output for Iris Xe integerate GPU, with PCI ID 0x9a49
+    # Output for Iris Xe integrate GPU, with PCI ID 0x9a49
     # (corresponding decimal value: 39497)
     In [3]: dpctl.utils.intel_device_info(d_gpu)
     Out[3]:

pulls/2304/_sources/contributor_guides/building.rst.txt

@@ -209,7 +209,7 @@ library.
     pushd build || exit 1
 
     INSTALL_PREFIX=$(pwd)/../install
-    rm -rf ${INSTALL_PREFIX}
+    rm -rf "${INSTALL_PREFIX}"
     export ONEAPI_ROOT=/opt/intel/oneapi
     # Values are set as appropriate for oneAPI DPC++ 2024.0
     # or later.

pulls/2304/_sources/index.rst.txt

@@ -56,7 +56,7 @@ Intel(R) oneAPI :dpcpp_compiler:`DPC++ compiler <>`.
 
             Access API Reference
 
-    .. grid-item-card:: Contibutor Guides
+    .. grid-item-card:: Contributor Guides
 
         The contributing guidelines will suggest a process of
         contributing to :mod:`dpctl`.

pulls/2304/_sources/user_guides/basic_concepts.rst.txt

@@ -111,7 +111,7 @@ backend. The context is required to map unified address space pointer to the dev
 where it was allocated unambiguously.
 
 In order for two DPC++-based Python extensions to share USM allocations, they each
-must use the `same` SYCL context when submitting for execution programs that would
+must use the *same* SYCL context when submitting for execution programs that would
 access this allocation.
 
 Since ``sycl::context`` is dynamically constructed by each extension  sharing a USM allocation,

pulls/2304/api_reference/dpctl/filter_selector_string.html

@@ -598,7 +598,7 @@
 <p><code class="docutils literal notranslate"><span class="pre">Backend</span></code> specifies the desired backend of targeted devices, while
 <code class="docutils literal notranslate"><span class="pre">DeviceType</span></code> specifies the type of targeted devices.
 <code class="docutils literal notranslate"><span class="pre">RelativeDeviceNumber</span></code> refers to the number of the device that matches
-any other given requirements, starting from <cite>0</cite> to marking the
+any other given requirements, starting from 0 to marking the
 “first device that matches the requirements”.</p>
 <p>Attempting to use a non-conforming string in places where filter selector
 string is expected will raise an exception.</p>

pulls/2304/api_reference/dpctl/generated/generated/dpctl.SyclDevice.create_sub_devices.html

@@ -584,7 +584,7 @@
 <h1>dpctl.SyclDevice.create_sub_devices<a class="headerlink" href="#dpctl-sycldevice-create-sub-devices" title="Permalink to this heading">¶</a></h1>
 <dl class="py method">
 <dt class="sig sig-object py" id="dpctl.SyclDevice.create_sub_devices">
-<span class="sig-prename descclassname"><span class="pre">SyclDevice.</span></span><span class="sig-name descname"><span class="pre">create_sub_devices</span></span><span class="sig-paren">(</span><em class="sig-param"><span class="n"><span class="pre">partition</span></span><span class="o"><span class="pre">=</span></span><span class="default_value"><span class="pre">parition_spec</span></span></em><span class="sig-paren">)</span><a class="headerlink" href="#dpctl.SyclDevice.create_sub_devices" title="Permalink to this definition">¶</a></dt>
+<span class="sig-prename descclassname"><span class="pre">SyclDevice.</span></span><span class="sig-name descname"><span class="pre">create_sub_devices</span></span><span class="sig-paren">(</span><em class="sig-param"><span class="n"><span class="pre">partition</span></span><span class="o"><span class="pre">=</span></span><span class="default_value"><span class="pre">partition_spec</span></span></em><span class="sig-paren">)</span><a class="headerlink" href="#dpctl.SyclDevice.create_sub_devices" title="Permalink to this definition">¶</a></dt>
 <dd><p>Creates a list of sub-devices by partitioning a root device based on the
 provided partition specifier.</p>
 <p>A partition specifier must be provided using a <code class="docutils literal notranslate"><span class="pre">partition</span></code>

pulls/2304/api_reference/dpctl_cmake.html

@@ -582,7 +582,7 @@
         <article role="main" id="furo-main-content">
           <section id="cmake-support">
 <span id="dpctl-cmake-support"></span><h1>CMake support<a class="headerlink" href="#cmake-support" title="Permalink to this heading">¶</a></h1>
-<p><a class="reference internal" href="dpctl/index.html#module-dpctl" title="dpctl"><code class="xref py py-mod docutils literal notranslate"><span class="pre">dpctl</span></code></a> comes with the configuration file <cite>dpctl-config.cmake</cite> which is installed
+<p><a class="reference internal" href="dpctl/index.html#module-dpctl" title="dpctl"><code class="xref py py-mod docutils literal notranslate"><span class="pre">dpctl</span></code></a> comes with the configuration file <code class="file docutils literal notranslate"><span class="pre">dpctl-config.cmake</span></code> which is installed
 on the <a class="reference external" href="https://cmake.org/cmake/help/latest/command/find_package.html">standard search path CMake uses to search for packages</a>.</p>
 <p>To build your extension that leverages <a class="reference internal" href="dpctl/index.html#module-dpctl" title="dpctl"><code class="xref py py-mod docutils literal notranslate"><span class="pre">dpctl</span></code></a>, include the following line in your CMake script:</p>
 <div class="highlight-cmake notranslate"><div class="highlight"><pre><span></span><span class="nb">find_package</span><span class="p">(</span><span class="s2">&quot;Dpctl&quot;</span><span class="w"> </span><span class="s">REQUIRED</span><span class="p">)</span>