Fix doc bullet points

Author: axiotisk

docs/advanced/accelerator.rst

@@ -82,6 +82,10 @@ VitisAccelerator Backend
 
 The ``vitis accelerator`` backned makes use of the vitis kernel flow to and streamlines the generation of an hls4ml project targeting PCIe accelerators.
 Vitis accelerator backend supports the following boards:
+<<<<<<< Updated upstream
+=======
+
+>>>>>>> Stashed changes
 * `alveo u55c <https://www.xilinx.com/products/boards-and-kits/alveo/u55c.html>`
 * `alveo-u50 <https://www.xilinx.com/products/boards-and-kits/alveo/u50.html>`
 * `alveo u250 <https://www.xilinx.com/products/boards-and-kits/alveo/u250.html>`
@@ -91,7 +95,11 @@ The backend generates an OpenCL host code that uploads and runs the kernel on th
 Example
 =======
 
+<<<<<<< Updated upstream
 The following example is a modified version of `hsl4ml example 7 <https://github.com/fastmachinelearning/hls4ml-tutorial/blob/master/part7_deployment.ipynb>`.
+=======
+The following example is a modified version of `hsl4ml example 7 <https://github.com/fastmachinelearning/hls4ml-tutorial/blob/master/part7_deployment.ipynb>`_.
+>>>>>>> Stashed changes
 
 .. code-block:: Python
 
@@ -110,6 +118,10 @@ The following example is a modified version of `hsl4ml example 7 <https://github
     hls_model.build()
 
 By default the build method generates all the necessary files to run the kernel on the accelerator board. As this can be a long process, there are three build options that target the generation of specific parts of the project:
+<<<<<<< Updated upstream
+=======
+
+>>>>>>> Stashed changes
 * `host` produces only the host code application
 * `hls` produces only the kernel object file `.xo`
 * `xclbin` produces only the kernel `.xclbin` file