diff --git a/include/Refresh.h b/include/Refresh.h
index 62eb51d..8626533 100644
--- a/include/Refresh.h
+++ b/include/Refresh.h
@@ -588,7 +588,7 @@ typedef struct Refresh_GraphicsPipelineCreateInfo
  * loadOp: Determines what is done with the texture slice at the beginning of the render pass.
  *
  *   LOAD:
- *     Loads the texture slice.
+ *     Loads the data currently in the texture slice.
  *
  *   CLEAR:
  *     Clears the texture slice to a single color.
@@ -613,7 +613,7 @@ typedef struct Refresh_GraphicsPipelineCreateInfo
  * writeOption:
  *  SAFEDISCARD:
  *    If this texture slice has been used in commands that have not completed,
- *    those commands will still be valid at the cost of increased memory usage.
+ *    this option will prevent a data dependency at the cost of increased memory usage.
  *    You may NOT assume that any of the previous texture data is retained.
  *    If the texture slice was not in use, this option is equivalent to SAFEOVERWRITE.
  *    This is a good option to prevent stalls when frequently reusing a texture slice in rendering.
@@ -1161,7 +1161,7 @@ REFRESHAPI void Refresh_BeginCopyPass(
  * writeOption:
  *  SAFEDISCARD:
  *    If the destination resource has been used in commands that have not completed,
- *    the issued commands will still be valid at the cost of increased memory usage.
+ *    this option will prevent a data dependency at the cost of increased memory usage.
  *    You may NOT assume that any of the previous data is retained.
  *    If the destination resource was not in use, this option is equivalent to SAFEOVERWRITE.
  * 	  This is a good option to prevent stalls on resources with frequent updates.
@@ -1239,7 +1239,7 @@ REFRESHAPI void Refresh_DownloadFromBuffer(
  * writeOption:
  *  SAFEDISCARD:
  *    If the destination resource has been used in commands that have not completed,
- *    the issued commands will still be valid at the cost of increased memory usage.
+ *    this option will prevent a data dependency at the cost of increased memory usage.
  *    You may NOT assume that any of the previous data is retained.
  *    If the destination resource was not in use, this option is equivalent to SAFEOVERWRITE.
  * 	  This is a good option to prevent stalls on resources with frequent updates.