WIP

.markdownlint-cli2.yaml

@@ -12,4 +12,5 @@ config:
   MD041: false
   MD051: false
 ignores:
+  - RELEASE.md
   - docs/doxygen/mainpage.md

.wordlist.txt

@@ -13,6 +13,8 @@ fatbinary
 GPGPU
 hardcoded
 hipcc
+hipother
+icc
 Interoperation
 latencies
 Malloc
@@ -23,4 +25,5 @@ Numa
 PTX
 RTC
 SIMT
-SYCL
+SYCL
+typedefs

docs/how-to/faq.md

@@ -216,7 +216,7 @@ dim3 grid1; x=1, y=1, z=1
 dim3 grid2 = {1,1,1}; x=1, y=1, z=1
 ```
 
-In which "dim3 grid1;" will yield a dim3 grid with all dimensional members x,y,z initalized to 1, as the default constructor behaves that way.
+In which "dim3 grid1;" will yield a dim3 grid with all dimensional members x,y,z initialized to 1, as the default constructor behaves that way.
 Further, if written:
 
 ```cpp
@@ -270,7 +270,7 @@ HIP_COMPILER=cuda
 HIP_RUNTIME=nvcc
 ```
 
-One symptom of this problem is the message "error: 'unknown error'(11) at square.hipref.cpp:56".  This can occur if you have a CUDA installation on an AMD platform, and HIP incorrectly detects the platform as nvcc.  HIP may be able to compile the application using the nvcc tool-chain but will generate this error at runtime since the platform does not have a CUDA device.
+One symptom of this problem is the message "error: 'unknown error'(11) at `square.hipref.cpp:56`.  This can occur if you have a CUDA installation on an AMD platform, and HIP incorrectly detects the platform as nvcc.  HIP may be able to compile the application using the nvcc tool-chain but will generate this error at runtime since the platform does not have a CUDA device.
 
 ## On CUDA, can I mix CUDA code with HIP code?
 
@@ -281,7 +281,7 @@ One notable exception is that `hipError_t` is a new type, and cannot be used whe
 `hipCUDAErrorTohipError`
 `hipCUResultTohipError`
 
-If platform portability is important, use #ifdef __HIP_PLATFORM_NVIDIA__ to guard the CUDA-specific code.
+If platform portability is important, use `#ifdef __HIP_PLATFORM_NVIDIA__` to guard the CUDA-specific code.
 
 ## How do I trace HIP application flow?
 
@@ -311,7 +311,7 @@ Previously, it was essential to declare dynamic shared memory using the HIP_DYNA
 Now, the HIP-Clang compiler provides support for extern shared declarations, and the HIP_DYNAMIC_SHARED option is no longer required. You may use the standard extern definition:
 extern __shared__ type var[];
 
-## I have multiple HIP enabled devices and I am getting an error code hipErrorSharedObjectInitFailed with the message "Error: shared object initialization failed"?
+## I have multiple HIP enabled devices and I am getting an error code `hipErrorSharedObjectInitFailed` with the message "Error: shared object initialization failed"?
 
 This error message is seen due to the fact that you do not have valid code object for all of your devices.
 
@@ -337,7 +337,7 @@ Once source is compiled with per-thread default stream enabled, all APIs will be
 
 Besides, per-thread default stream be enabled per translation unit, users can compile some files with feature enabled and some with feature disabled. Feature enabled translation unit will have default stream as per thread and there will not be any implicit synchronization done but other modules will have legacy default stream which will do implicit synchronization.
 
-## How to use complex muliplication and division operations?
+## How to use complex multiplication and division operations?
 
 In HIP, `hipFloatComplex` and `hipDoubleComplex` are defined as complex data types,