issue #6945: refactoring docs for management api on merchant backend service

1 files changed, 5 insertions, 5 deletions

diff --git a/taler-mcig.rst b/taler-mcig.rst
index f93d3d15..e7c89a67 100644
--- a/taler-mcig.rst
+++ b/taler-mcig.rst
@@ -151,24 +151,24 @@ are demonstrated in the next section.
   which you may choose to pay or to pass on to the customer.
   This can be configured to a maximum amount, per order.
 
-  You can set ``default_max_deposit_fee`` in :http:post:`/private/instances`,
+  You can set ``default_max_deposit_fee`` in :http:post:`/management/instances`,
   or override the default by setting ``max_fee`` when creating an order.
 
   There is also the *wire fee* (see step 6, above),
   which you may choose to pay or to pass on to the customer.
 
-  You can set ``default_max_wire_fee`` in :http:post:`/private/instances`,
+  You can set ``default_max_wire_fee`` in :http:post:`/management/instances`,
   and ``max_wire_fee`` in the contract.
   If unspecified, the default value is zero (meaning you bear the entire fee).
 
   You can *amortize* the wire fee across a number of customers
-  by setting ``default_wire_fee_amortization`` in :http:post:`/private/instances`,
+  by setting ``default_wire_fee_amortization`` in :http:post:`/management/instances`,
   and ``wire_fee_amortization`` in the contract.
   This is the number of customer transactions over which you expect to
   amortize wire fees on average.
   If unspecified, the default value is one.
 
-  .. Note:: :http:post:`/private/instances` must be done at
+  .. Note:: :http:post:`/management/instances` must be done at
      instance-setup time (prior to any purchase).
 
 **forgettable customer details**
@@ -287,7 +287,7 @@ above => refer to other guide, but of course specify how we can
 override defaults from instance setup per-order.)
 
 
-M: :http:post:`/private/instances`
+M: :http:post:`/management/instances`
 
 .. code-block:: javascript