diff --git a/static/docs/commands-reference/push.md b/static/docs/commands-reference/push.md
index ada58475c4..e503d332f5 100644
--- a/static/docs/commands-reference/push.md
+++ b/static/docs/commands-reference/push.md
@@ -24,7 +24,9 @@ environments and preserving data versions (input datasets, intermediate results,
 models, metrics, etc) remotely (S3, SSH, GCS, etc) are the most common use cases
 for these commands.
 
-The `dvc push` command allows one to upload data to remote storage.
+The `dvc push` command allows one to upload data to remote storage. It doesn't
+save any changes in the code or DVC-files. Those should be saved by using
+`git commit` and `git push`. 
 
 Under the hood a few actions are taken:
 
diff --git a/static/docs/get-started/share-data.md b/static/docs/get-started/share-data.md
index b152b3b4f7..88f864ba74 100644
--- a/static/docs/get-started/share-data.md
+++ b/static/docs/get-started/share-data.md
@@ -15,6 +15,10 @@ pulled by your team or you when you need it.
 Usually, you run it along with `git commit` and `git push` to save changed
 [DVC-files](/doc/user-guide/dvc-file-format) to Git.
 
+The `dvc push` command allows one to upload data to remote storage. It doesn't
+save any changes in the code or DVC-files. Those should be saved by using      
+`git commit` and `git push`.
+
 See `dvc push` for more details and options for this command.
 
 > \*As noted in the DVC [configuration](/doc/get-started/configure) chapter, we