diff --git a/docs/usage/pitr-physical.md b/docs/usage/pitr-physical.md
index 21e0e80d..b2a20700 100644
--- a/docs/usage/pitr-physical.md
+++ b/docs/usage/pitr-physical.md
@@ -18,6 +18,9 @@ Percona Backup for MongoDB recognizes if it is a full or an incremental backup a
 
 You can [track the restore progress](restore-progress.md) using the `pbm describe-restore` command. Don't run any other commands since they may interrupt the restore flow and cause the issues with the database.
 
+```bash
+pbm describe-restore <restore_name> -c pbm_config.yaml
+```
 
 !!! note    
 
diff --git a/docs/usage/restore-physical.md b/docs/usage/restore-physical.md
index d4c78823..f24ad412 100644
--- a/docs/usage/restore-physical.md
+++ b/docs/usage/restore-physical.md
@@ -54,6 +54,10 @@
 
 3. [Track the restore progress](restore-progress.md) using the `pbm describe-restore` command. Don't run any other commands since they may interrupt the restore flow and cause the issues with the database.
 
+    ```bash
+    pbm describe-restore <restore_name> -c pbm_config.yaml
+    ```
+
 A restore has the `Done` status when it succeeded on all nodes. 
 
 If it failed on some nodes, it has the `partlyDone` status but you can still start the cluster. The failed nodes will receive the data via the initial sync. Learn more about partially done restores in the [Partially done physical restores](../troubleshoot/restore-partial.md) chapter.