Skip to content

Commit

Permalink
Apply suggestions from code review
Browse files Browse the repository at this point in the history
Co-authored-by: randyh62 <[email protected]>
  • Loading branch information
neon60 and randyh62 authored Oct 18, 2024
1 parent d6bc663 commit 579f698
Show file tree
Hide file tree
Showing 2 changed files with 6 additions and 6 deletions.
8 changes: 4 additions & 4 deletions docs/how-to/hip_runtime_api/error_handling.rst
Original file line number Diff line number Diff line change
Expand Up @@ -20,12 +20,12 @@ and :cpp:func:`hipGetErrorName()` can be used.
Error handling usage
================================================================================

Error handling functions enable developers to implement appropriate error
handling strategies, such as retry mechanisms, resource cleanup, or graceful
Error handling functions enable developers to implement appropriate strategies
for handling errors, such as retry mechanisms, resource cleanup, or graceful
degradation.

The descriptions of the important :ref:`error handling functions <error_handling_reference>`
are the following:
Descriptions of the important :ref:`error handling functions <error_handling_reference>`
are as follows:

* :cpp:func:`hipGetLastError` returns the last error that occurred during a HIP
runtime API call and resets the error code to :cpp:enumerator:`hipSuccess`.
Expand Down
4 changes: 2 additions & 2 deletions docs/how-to/hip_runtime_api/initialization.rst
Original file line number Diff line number Diff line change
Expand Up @@ -34,8 +34,8 @@ to be able to control the timing of the initialization.
Querying and setting GPUs
================================================================================

If multiple GPUs are available, it's worth to query and select the desired GPU(s)
based on properties.
If multiple GPUs are available in the system, you can query and select the desired GPU(s) to use
based on device properties, such as ...

Querying GPUs
--------------------------------------------------------------------------------
Expand Down

0 comments on commit 579f698

Please sign in to comment.