docs: fix typos and missing articles in known issues section

Fix missing period, double space, missing articles, and missing comma
in the known issues section of the 7.13.0 release notes.

(cherry picked from commit 86f3b4be067e476bef2f7642c85070140d0a1bdb)

Author: pmoutsias-amd

docs/about/release-notes.md

@@ -490,11 +490,11 @@ ROCm known issues are noted on {fab}`github` [GitHub](https://github.com/ROCm/RO
 
 ### ROCm Compute Profiler might fail when profiling bash script or command
 
-Running a bash script or command as a target for ROCm Compute Profiler might fail because bash overwrites the required environment variables. As a workaround, use `--no-native-tool` option in the profile mode. Note that this will disable iteration multiplexing.
+Running a bash script or command as a target for ROCm Compute Profiler might fail because bash overwrites the required environment variables. As a workaround, use the `--no-native-tool` option in the profile mode. Note that this will disable iteration multiplexing.
 
 ### hipFFT and rocFFT callback examples fail to build on Windows
 
-The hipFFT and rocFFT callback examples in [rocm-examples](https://github.com/rocm/rocm-examples) fail to build on a Windows operating system due to a linker error. CMake configuration and HIP object compilation will complete successfully, but the final link step fails with `clang: error: invalid linker name in argument '-fuse-ld=lld-link'` This issue affects all Windows configurations using Relocatable Device Code (RDC) mode. Linux builds are not affected. As a workaround, skip the hipFFT and rocFFT callback examples on Windows, and refer to the Linux builds or [callback](https://github.com/ROCm/rocm-examples/tree/amd-staging/Libraries/rocFFT/callback/) functionality documentation.
+The hipFFT and rocFFT callback examples in [rocm-examples](https://github.com/rocm/rocm-examples) fail to build on a Windows operating system due to a linker error. CMake configuration and HIP object compilation will complete successfully, but the final link step fails with `clang: error: invalid linker name in argument '-fuse-ld=lld-link'`. This issue affects all Windows configurations using Relocatable Device Code (RDC) mode. Linux builds are not affected. As a workaround, skip the hipFFT and rocFFT callback examples on Windows, and refer to the Linux builds or [callback](https://github.com/ROCm/rocm-examples/tree/amd-staging/Libraries/rocFFT/callback/) functionality documentation.
 
 ### QMCPACK might become unresponsive during DMC simulation on AMD Instinct MI300A GPUs
 
@@ -510,16 +510,16 @@ Applications targeting multiple AMD GPU architectures might observe significantl
 
 ### HIP cooperative groups might fail when compiled using the SPIR-V path
 
-HIP applications that use cooperative groups might fail at kernel launch when compiled with `--offload-arch=amdgcnspirv`. The application fails at runtime with `LLVM ERROR: Cannot select: intrinsic %llvm.amdgcn.s.wait.asynccnt` error message. This
+HIP applications that use cooperative groups might fail at kernel launch when compiled with `--offload-arch=amdgcnspirv`. The application fails at runtime with the `LLVM ERROR: Cannot select: intrinsic %llvm.amdgcn.s.wait.asynccnt` error message. This
 affects all GPU architectures when using the SPIR-V compilation path. As a workaround, compile using a direct GPU architecture target (for example, `--offload-arch=gfx942`) instead of `--offload-arch=amdgcnspirv`.
 
 ### Illegal memory address error when using placement new with device function returns
 
-HIP kernels that use the placement new operators to construct objects in the `hipMalloc` device memory might crash with `hipErrorIllegalAddress` error message when you pass a `__device__` function return value as the constructor argument. This only affects non-trivially-copyable types (for example, types with user-defined or deleted copy/move constructors). Trivially-copyable types are not affected. As a workaround, assign the device function return value to a local variable before passing it to placement new.
+HIP kernels that use the placement new operators to construct objects in the `hipMalloc` device memory might crash with the `hipErrorIllegalAddress` error message when you pass a `__device__` function return value as the constructor argument. This only affects non-trivially-copyable types (for example, types with user-defined or deleted copy/move constructors). Trivially-copyable types are not affected. As a workaround, assign the device function return value to a local variable before passing it to placement new.
 
 ### LLVM-based compilers might fail when compiling half-precision vector operations
 
-LLVM-based compilers might fail, returning `Failed to find subregs!` error message in `SIInstrInfo::copyPhysReg`, when compiling half-precision vector operations with optimization enabled. The issue was observed at optimization levels `-O1` to `-O3`.
+LLVM-based compilers might fail, returning the `Failed to find subregs!` error message in `SIInstrInfo::copyPhysReg`, when compiling half-precision vector operations with optimization enabled. The issue was observed at optimization levels `-O1` to `-O3`.
 
 ### hipBLAS test suites failure on Windows
 
@@ -539,15 +539,15 @@ sudo apt install amdrocm-*
 
 ### Issues related to AddressSanitizer
 
-Multiple issues associated with AddressSanitizer (ASAN) `-fsanitize=address` being enabled have been observed including:
+Multiple issues associated with AddressSanitizer (ASAN) `-fsanitize=address` being enabled have been observed, including:
 
 #### ASAN reports false errors for GPU kernels using shared memory
 
-When you compile GPU kernels with ASAN enabled, kernels that use `__shared__` memory might produce false heap-buffer-overflow errors or GPU memory faults. As a workaround, disable ASAN by removing `-fsanitize=address` setting for affected kernels.
+When you compile GPU kernels with ASAN enabled, kernels that use `__shared__` memory might produce false heap-buffer-overflow errors or GPU memory faults. As a workaround, disable ASAN by removing the `-fsanitize=address` setting for affected kernels.
 
 #### GPU kernels fail to launch in ASAN builds with large thread counts
 
-When you build GPU libraries with ASAN enabled, kernels configured with large thread counts might fail to launch with `HSA_STATUS_ERROR_INVALID_ISA` error. As a workaround, reduce the thread block sizes to 256 threads or fewer for ASAN builds. The issue is currently under investigation.
+When you build GPU libraries with ASAN enabled, kernels configured with large thread counts might fail to launch with an `HSA_STATUS_ERROR_INVALID_ISA` error. As a workaround, reduce the thread block sizes to 256 threads or fewer for ASAN builds. The issue is currently under investigation.
 
 #### ASAN breaks multi-architecture HIP binary builds
 
@@ -562,7 +562,7 @@ auto local_arg = kernel_arg;
 result = condition ? local_arg : other_arg;
 ```
 
-Alternatively, disable ASAN by removing `-fsanitize=address`  when compiling GPU kernels.
+Alternatively, disable ASAN by removing `-fsanitize=address` when compiling GPU kernels.
 
 ## ROCm resolved issues