diff --git a/docs/sysadm/deployment/howto-process-add-forge-now-requests.rst b/docs/sysadm/deployment/howto-process-add-forge-now-requests.rst
index 65fb5867bd40b58b498660d7e4efc551326afcbd..27c0900e5aaeebfad58ad37ccbad29bbb464926f 100644
--- a/docs/sysadm/deployment/howto-process-add-forge-now-requests.rst
+++ b/docs/sysadm/deployment/howto-process-add-forge-now-requests.rst
@@ -42,7 +42,6 @@ On a staging node (usually the scheduling node of the domain), run:
        register-lister gitea \
          url=<url>
 
-
 For example, forge `git.afpy.org <https://git.afpy.org>`_ which is a `gitea
 <https://gitea.io/en-us/>`_ instance, we'd run:
 
@@ -58,6 +57,31 @@ For example, forge `git.afpy.org <https://git.afpy.org>`_ which is a `gitea
    INFO:swh.lister.pattern:Reached page limit of 3, terminating
 
 
+Note that the cli accepts the ``instance`` parameter instead of the full url. So, for
+some forges ``gitea``, ``gogs`` or ``gitlab`` (which uses some api endpoints), it might
+be simpler to use it directly to avoid typos on their api urls.
+
+.. code::
+
+   swh scheduler --url http://scheduler0.internal.staging.swh.network:5008/ \
+     add-forge-now --preset staging \
+       register-lister gitea \
+         instance=<instance>
+
+That way, the previous example becomes a tad simpler:
+
+.. code::
+
+   swh scheduler --url http://scheduler0.internal.staging.swh.network:5008/ \
+     add-forge-now --preset staging \
+       register-lister gitea \
+         instance=git.afpy.org
+
+   INFO:swh.lister.pattern:Max origins per page set, truncated 36 page results down to 30
+   INFO:swh.lister.pattern:Disabling origins before sending them to the scheduler
+   INFO:swh.lister.pattern:Reached page limit of 3, terminating
+
+
 Ensure the :ref:`lister got registered<check-lister-is-registered>` in the staging
 scheduler db.
 
@@ -120,7 +144,7 @@ For example:
    swh scheduler --url http://saatchi.internal.softwareheritage.org:5008/ \
      add-forge-now ( --preset production ) \
      register-lister gitea \
-       url=https://git.afpy.org/api/v1/
+       instance=git.afpy.org
 
 Ensure the :ref:`lister got registered<check-lister-is-registered>` in the production
 scheduler db.