diff --git a/docs/source/restore/index.rst b/docs/source/restore/index.rst
index ab5ba5951..c330c4d02 100644
--- a/docs/source/restore/index.rst
+++ b/docs/source/restore/index.rst
@@ -48,18 +48,39 @@ ScyllaDB Manager Restore command supports the following features:
 * Progress tracking (:ref:`sctool progress <task-progress>`, Prometheus metrics, `Scylla Monitoring <https://monitoring.docs.scylladb.com>`_ Manager dashboard)
 * :ref:`Pausing <task-stop>` and :ref:`resuming <task-start>` at any point of the process
 
-Restore speed and granularity
-=============================
+Restore speed observability
+===========================
+
+| Restore speed can be checked with :ref:`sctool progress <task-progress>` command.
+| It displays average per shard download and load&stream bandwidths. When used with ``--details`` flag, it also displays per host bandwidths.
+
+Restore speed can be also observed with Prometheus metrics:
+
+* ``scylla_manager_restore_remaining_bytes``
+* ``scylla_manager_restore_downloaded_bytes``
+* ``scylla_manager_restore_download_duration``
+* ``scylla_manager_restore_streamed_bytes``
+* ``scylla_manager_restore_stream_duration``
+
+Restore speed control
+=====================
 
 .. _restore-speed-and-granularity:
 
-Restore speed is controlled by two parameters: ``--parallel`` and ``--batch-size``.
-Parallel specifies how many nodes can be used in restore procedure at the same time.
-Batch size specifies how many SSTable bundles can be restored from backup location in a single job.
-Note that increasing the default batch size might significantly increase restore performance,
-as only one shard can work on restoring a single SSTable bundle.
+Restore speed is controlled by many parameters (see :ref:`sctool restore <sctool-restore>` documentation for details):
+
+* ``--batch-size``
+* ``--parallel``
+* ``--transfers``
+* ``--unpin-agent-cpu``
+* ``--allow-compaction``
+
+| Most of those parameters have default values chosen for restoring as fast as possible.
+| You should need to change them only when you want to limit the impact that the restore has on a cluster serving traffic on not currently restored tables.
 
-Those parameters can be set when you:
+| For backward compatibility reasons, the default value of ``--batch-size`` is ``2``, but it should be changed to ``0`` when you want to maximize restore speed.
+| Note that with bigger batch size comes lesser granularity. This means that pausing and resuming restore would need to perform more work.
 
-* Schedule a restore with :ref:`sctool restore <sctool-restore>`
-* Update a restore specification with :ref:`sctool restore update <restore-update>`
+The ``--unpin-agent-cpu`` is disabled by default, but in case you observe small download
+bandwidth, you could try to :ref:`pause <task-stop>` restore task, :ref:`update <restore-update>` it with ``--unpin-agent-cpu``,
+and :ref:`resume <task-start>` it.