diff --git a/core/modules/node/node.api.php b/core/modules/node/node.api.php
index 2324b47..b4e50e8 100644
--- a/core/modules/node/node.api.php
+++ b/core/modules/node/node.api.php
@@ -511,6 +511,14 @@ function hook_node_revision_delete($node) {
  * node table in the database, after the type-specific hook_insert() is invoked,
  * and after field_attach_insert() is called.
  *
+ * Note that at the time, when this hook is invoked, no changes were actually
+ * written to the database. This will be done when save operation is entirely
+ * completed and node_save() goes out of scope. You should not rely on data in
+ * the database at this time as it may be out of date. You should also note,
+ * that any write/update database queries, that will be run from this hook,
+ * will also not be committed immediately. Check node_save() and
+ * db_transaction() for more info.
+ *
  * @param $node
  *   The node that is being created.
  *
@@ -697,6 +705,14 @@ function hook_node_presave($node) {
  * table in the database, after the type-specific hook_update() is invoked, and
  * after field_attach_update() is called.
  *
+ * Note that at the time, when this hook is invoked, no changes were actually
+ * written to the database. This will be done when save operation is entirely
+ * completed and node_save() goes out of scope. You should not rely on data in
+ * the database at this time as it may be out of date. You should also note,
+ * that any write/update database queries, that will be run from this hook,
+ * will also not be committed immediately. Check node_save() and
+ * db_transaction() for more info.
+ *
  * @param $node
  *   The node that is being updated.
  *
diff --git a/core/modules/user/user.api.php b/core/modules/user/user.api.php
index dc16906..df2270b 100644
--- a/core/modules/user/user.api.php
+++ b/core/modules/user/user.api.php
@@ -256,6 +256,14 @@ function hook_user_presave(&$edit, $account) {
  * The module should save its custom additions to the user object into the
  * database.
  *
+ * Note that at the time, when this hook is invoked, no changes were actually
+ * written to the database. This will be done when save operation is entirely
+ * completed and user_save() goes out of scope. You should not rely on data in
+ * the database at this time as it may be out of date. You should also note,
+ * that any write/update database queries, that will be run from this hook,
+ * will also not be committed immediately. Check user_save() and
+ * db_transaction() for more info.
+ *
  * @param $edit
  *   The array of form values submitted by the user.
  * @param $account
@@ -279,6 +287,14 @@ function hook_user_insert(&$edit, $account) {
  * Modules may use this hook to update their user data in a custom storage
  * after a user account has been updated.
  *
+ * Note that at the time, when this hook is invoked, no changes were actually
+ * written to the database. This will be done when save operation is entirely
+ * completed and user_save() goes out of scope. You should not rely on data in
+ * the database at this time as it may be out of date. You should also note,
+ * that any write/update database queries, that will be run from this hook,
+ * will also not be committed immediately. Check user_save() and
+ * db_transaction() for more info.
+ *
  * @param $edit
  *   The array of form values submitted by the user.
  * @param $account