Make small updates to READMEs

Author: justin-rosner

DirectProgramming/C++SYCL_FPGA/ReferenceDesigns/fft2d/README.md

@@ -216,39 +216,29 @@ Additionally, the `cmake` build system can be configured using the following par
 
 ### On Linux
 
-#### Run on FPGA Emulator
-
 1. Run the sample on the FPGA emulator (the kernel executes on the CPU).
    ```
    ./fft2d.fpga_emu
    ```
 
-#### Run on FPGA Simulator
-
-1. Run the sample on the FPGA simulator.
+2. Run the sample on the FPGA simulator.
    ```
    CL_CONTEXT_MPSIM_DEVICE_INTELFPGA=1 ./fft2d.fpga_sim
    ```
 
-#### Run on FPGA
-
-1. Run the sample on the FPGA device (only if you ran `cmake` with `-DFPGA_DEVICE=<board-support-package>:<board-variant>`).
+3. Run the sample on the FPGA device (only if you ran `cmake` with `-DFPGA_DEVICE=<board-support-package>:<board-variant>`).
    ```
    ./fft2d.fpga
    ```
 
 ### On Windows
 
-#### Run on FPGA Emulator
-
 1. Run the sample on the FPGA emulator (the kernel executes on the CPU).
    ```
    fft2d.fpga_emu.exe
    ```
 
-#### Run on FPGA Simulator
-
-1. Run the sample on the FPGA simulator.
+2. Run the sample on the FPGA simulator.
    ```
    set CL_CONTEXT_MPSIM_DEVICE_INTELFPGA=1
    fft2d.fpga_sim.exe

DirectProgramming/C++SYCL_FPGA/ReferenceDesigns/matmul/README.md

@@ -307,39 +307,29 @@ You can perform the multiplication of the set of matrices repeatedly. This step
 
 ### On Linux
 
-#### Run on FPGA Emulator
-
 1. Run the sample on the FPGA emulator (the kernel executes on the CPU).
    ```
    ./matmul.fpga_emu
    ```
 
-#### Run on FPGA Simulator
-
-1. Run the sample on the FPGA simulator.
+2. Run the sample on the FPGA simulator.
    ```
    CL_CONTEXT_MPSIM_DEVICE_INTELFPGA=1 ./matmul.fpga_sim
    ```
 
-#### Run on FPGA
-
-1. Run the sample on the FPGA device (only if you ran `cmake` with `-DFPGA_DEVICE=<board-support-package>:<board-variant>`).
+3. Run the sample on the FPGA device (only if you ran `cmake` with `-DFPGA_DEVICE=<board-support-package>:<board-variant>`).
    ```
    ./matmul.fpga
    ```
 
 ### On Windows
 
-#### Run on FPGA Emulator
-
 1. Run the sample on the FPGA emulator (the kernel executes on the CPU).
    ```
    matmul.fpga_emu.exe
    ```
 
-#### Run on FPGA Simulator
-
-1. Run the sample on the FPGA simulator.
+2. Run the sample on the FPGA simulator.
    ```
    set CL_CONTEXT_MPSIM_DEVICE_INTELFPGA=1
    matmul.fpga_sim.exe

DirectProgramming/C++SYCL_FPGA/ReferenceDesigns/pca/README.md

@@ -427,39 +427,29 @@ Additionally, the `cmake` build system can be configured using the following par
 
 ### On Linux
 
-#### Run on FPGA Emulator
-
 1. Run the sample on the FPGA emulator (the kernel executes on the CPU).
    ```
    ./pca.fpga_emu <path to data/abalone.csv>
    ```
 
-#### Run on FPGA Simulator
-
-1. Run the sample on the FPGA simulator.
+2. Run the sample on the FPGA simulator.
    ```
    CL_CONTEXT_MPSIM_DEVICE_INTELFPGA=1 ./pca.fpga_sim <path to data/abalone.csv>
    ```
 
-#### Run on FPGA
-
-1. Run the sample on the FPGA device (only if you ran `cmake` with `-DFPGA_DEVICE=<board-support-package>:<board-variant>`).
+3. Run the sample on the FPGA device (only if you ran `cmake` with `-DFPGA_DEVICE=<board-support-package>:<board-variant>`).
    ```
    ./pca.fpga <path to data/abalone.csv>
    ```
 
 ### On Windows
 
-#### Run on FPGA Emulator
-
 1. Run the sample on the FPGA emulator (the kernel executes on the CPU).
    ```
    pca.fpga_emu.exe <path to data/abalone.csv>
    ```
 
-#### Run on FPGA Simulator
-
-1. Run the sample on the FPGA simulator.
+2. Run the sample on the FPGA simulator.
    ```
    set CL_CONTEXT_MPSIM_DEVICE_INTELFPGA=1
    pca.fpga_sim.exe <path to data/abalone.csv>

DirectProgramming/C++SYCL_FPGA/ReferenceDesigns/qrd/README.md

@@ -253,43 +253,33 @@ You can perform the QR decomposition of the set of matrices repeatedly. This ste
 
 ### On Linux
 
-#### Run on FPGA Emulator
-
-1. Increase the amount of memory that the emulator runtime is permitted to allocate by exporting the `CL_CONFIG_CPU_FORCE_PRIVATE_MEM_SIZE` environment variable before running the executable.
-2. Run the sample on the FPGA emulator (the kernel executes on the CPU).
+1. Run the sample on the FPGA emulator (the kernel executes on the CPU).
    ```
    export CL_CONFIG_CPU_FORCE_PRIVATE_MEM_SIZE=32MB
    ./qrd.fpga_emu
    ```
+   * Increase the amount of memory that the emulator runtime is permitted to allocate by exporting the `CL_CONFIG_CPU_FORCE_PRIVATE_MEM_SIZE` environment variable before running the executable.
 
-#### Run on FPGA Simulator
-
-1. Run the sample on the FPGA simulator.
+2. Run the sample on the FPGA simulator.
    ```
    CL_CONTEXT_MPSIM_DEVICE_INTELFPGA=1 ./qrd.fpga_sim
    ```
 
-#### Run on FPGA
-
-1. Run the sample on the FPGA device (only if you ran `cmake` with `-DFPGA_DEVICE=<board-support-package>:<board-variant>`).
+3. Run the sample on the FPGA device (only if you ran `cmake` with `-DFPGA_DEVICE=<board-support-package>:<board-variant>`).
    ```
    ./qrd.fpga
    ```
 
 ### On Windows
 
-#### Run on FPGA Emulator
-
-1. Increase the amount of memory that the emulator runtime is permitted to allocate by setting the `CL_CONFIG_CPU_FORCE_PRIVATE_MEM_SIZE` environment variable before running the executable.
-2. Run the sample on the FPGA emulator (the kernel executes on the CPU).
+1. Run the sample on the FPGA emulator (the kernel executes on the CPU).
    ```
    set CL_CONFIG_CPU_FORCE_PRIVATE_MEM_SIZE=32MB
    qrd.fpga_emu.exe
    ```
+   * Increase the amount of memory that the emulator runtime is permitted to allocate by setting the `CL_CONFIG_CPU_FORCE_PRIVATE_MEM_SIZE` environment variable before running the executable.
 
-#### Run on FPGA Simulator
-
-1. Run the sample on the FPGA simulator.
+2. Run the sample on the FPGA simulator.
    ```
    set CL_CONTEXT_MPSIM_DEVICE_INTELFPGA=1
    qrd.fpga_sim.exe

DirectProgramming/C++SYCL_FPGA/ReferenceDesigns/qri/README.md

@@ -244,43 +244,33 @@ You can perform the QR-based inversion of the set of matrices repeatedly, as sho
 
 ### On Linux
 
-#### Run on FPGA Emulator
-
-1. Increase the amount of memory that the emulator runtime is permitted to allocate by exporting the `CL_CONFIG_CPU_FORCE_PRIVATE_MEM_SIZE` environment variable before running the executable.
-2. Run the sample on the FPGA emulator (the kernel executes on the CPU).
+1. Run the sample on the FPGA emulator (the kernel executes on the CPU).
    ```
    export CL_CONFIG_CPU_FORCE_PRIVATE_MEM_SIZE=32MB
    ./qri.fpga_emu
    ```
+   * Increase the amount of memory that the emulator runtime is permitted to allocate by exporting the `CL_CONFIG_CPU_FORCE_PRIVATE_MEM_SIZE` environment variable before running the executable.
 
-#### Run on FPGA Simulator
-
-1. Run the sample on the FPGA simulator.
+2. Run the sample on the FPGA simulator.
    ```
    CL_CONTEXT_MPSIM_DEVICE_INTELFPGA=1 ./qri.fpga_sim
    ```
 
-#### Run on FPGA
-
-1. Run the sample on the FPGA device (only if you ran `cmake` with `-DFPGA_DEVICE=<board-support-package>:<board-variant>`).
+3. Run the sample on the FPGA device (only if you ran `cmake` with `-DFPGA_DEVICE=<board-support-package>:<board-variant>`).
    ```
    ./qri.fpga
    ```
 
 ### On Windows
 
-#### Run on FPGA Emulator
-
-1. Increase the amount of memory that the emulator runtime is permitted to allocate by setting the `CL_CONFIG_CPU_FORCE_PRIVATE_MEM_SIZE` environment variable before running the executable.
-2. Run the sample on the FPGA emulator (the kernel executes on the CPU).
+1. Run the sample on the FPGA emulator (the kernel executes on the CPU).
    ```
    set CL_CONFIG_CPU_FORCE_PRIVATE_MEM_SIZE=32MB
    qri.fpga_emu.exe
    ```
+   * Increase the amount of memory that the emulator runtime is permitted to allocate by setting the `CL_CONFIG_CPU_FORCE_PRIVATE_MEM_SIZE` environment variable before running the executable.
 
-#### Run on FPGA Simulator
-
-1. Run the sample on the FPGA simulator.
+2. Run the sample on the FPGA simulator.
    ```
    set CL_CONTEXT_MPSIM_DEVICE_INTELFPGA=1
    qri.fpga_sim.exe

DirectProgramming/C++SYCL_FPGA/Tutorials/Tools/use_library/README.md

@@ -238,6 +238,8 @@ Note that the library files (\*.a) must be included after all of the cpp files i
    CL_CONTEXT_MPSIM_DEVICE_INTELFPGA=1 ./use_library.fpga_sim
    ```
 
+> **Note**: Running this sample on an actual FPGA device requires a BSP that supports host pipes. As there are currently no commercial BSPs with such support, only the SYCL HLS flow is enabled for this code sample.
+
 ### On Windows
 
 1. Run the sample on the FPGA emulator (the kernel executes on the CPU).