Final pass on platformization (#555)

source/administration/monitoring/publish-events-to-amqp.rst

@@ -191,7 +191,7 @@ the associated AMQP deployment as a target.
 3) Configure Bucket Notifications using the AMQP Endpoint as a Target
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Use the :mc-cmd:`mc event add` command to add a new bucket notification 
+Use the :mc:`mc event add` command to add a new bucket notification 
 event with the configured AMQP service as a target:
 
 .. code-block:: shell
@@ -206,7 +206,7 @@ event with the configured AMQP service as a target:
 - Replace ``EVENTS`` with a comma-separated list of :ref:`events 
   <mc-event-supported-events>` for which MinIO triggers notifications.
 
-Use :mc-cmd:`mc event list` to view all configured bucket events for 
+Use :mc:`mc event list` to view all configured bucket events for 
 a given notification target:
 
 .. code-block:: shell
@@ -224,7 +224,7 @@ when configuring the bucket notification.
 
 For example, if the bucket notification configuration includes the 
 ``s3:ObjectCreated:Put`` event, you can use the 
-:mc-cmd:`mc cp` command to create a new object in the bucket and trigger 
+:mc:`mc cp` command to create a new object in the bucket and trigger 
 a notification.
 
 .. code-block:: shell
@@ -353,7 +353,7 @@ specified when configuring the bucket notification.
 
 For example, if the bucket notification configuration includes the 
 ``s3:ObjectCreated:Put`` event, you can use the 
-:mc-cmd:`mc cp` command to create a new object in the bucket and trigger 
+:mc:`mc cp` command to create a new object in the bucket and trigger 
 a notification.
 
 .. code-block:: shell

source/administration/monitoring/publish-events-to-elasticsearch.rst

@@ -183,7 +183,7 @@ the associated Elasticsearch deployment as a target.
 3) Configure Bucket Notifications using the Elasticsearch Endpoint as a Target
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Use the :mc-cmd:`mc event add` command to add a new bucket notification 
+Use the :mc:`mc event add` command to add a new bucket notification 
 event with the configured Elasticsearch service as a target:
 
 .. code-block:: shell
@@ -198,7 +198,7 @@ event with the configured Elasticsearch service as a target:
 - Replace ``EVENTS`` with a comma-separated list of :ref:`events 
   <mc-event-supported-events>` for which MinIO triggers notifications.
 
-Use :mc-cmd:`mc event list` to view all configured bucket events for 
+Use :mc:`mc event list` to view all configured bucket events for 
 a given notification target:
 
 .. code-block:: shell
@@ -216,7 +216,7 @@ when configuring the bucket notification.
 
 For example, if the bucket notification configuration includes the 
 ``s3:ObjectCreated:Put`` event, you can use the 
-:mc-cmd:`mc cp` command to create a new object in the bucket and trigger 
+:mc:`mc cp` command to create a new object in the bucket and trigger 
 a notification.
 
 .. code-block:: shell
@@ -335,7 +335,7 @@ notification.
 
 For example, if the bucket notification configuration includes the 
 ``s3:ObjectCreated:Put`` event, you can use the 
-:mc-cmd:`mc cp` command to create a new object in the bucket and trigger 
+:mc:`mc cp` command to create a new object in the bucket and trigger 
 a notification.
 
 .. code-block:: shell

source/administration/monitoring/publish-events-to-kafka.rst

@@ -190,7 +190,7 @@ the associated Kafka deployment as a target.
 3) Configure Bucket Notifications using the Kafka Endpoint as a Target
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Use the :mc-cmd:`mc event add` command to add a new bucket notification 
+Use the :mc:`mc event add` command to add a new bucket notification 
 event with the configured Kafka service as a target:
 
 .. code-block:: shell
@@ -205,7 +205,7 @@ event with the configured Kafka service as a target:
 - Replace ``EVENTS`` with a comma-separated list of :ref:`events 
   <mc-event-supported-events>` for which MinIO triggers notifications.
 
-Use :mc-cmd:`mc event list` to view all configured bucket events for 
+Use :mc:`mc event list` to view all configured bucket events for 
 a given notification target:
 
 .. code-block:: shell
@@ -223,7 +223,7 @@ when configuring the bucket notification.
 
 For example, if the bucket notification configuration includes the 
 ``s3:ObjectCreated:Put`` event, you can use the 
-:mc-cmd:`mc cp` command to create a new object in the bucket and trigger 
+:mc:`mc cp` command to create a new object in the bucket and trigger 
 a notification.
 
 .. code-block:: shell
@@ -347,7 +347,7 @@ specified when configuring the bucket notification.
 
 For example, if the bucket notification configuration includes the 
 ``s3:ObjectCreated:Put`` event, you can use the 
-:mc-cmd:`mc cp` command to create a new object in the bucket and trigger 
+:mc:`mc cp` command to create a new object in the bucket and trigger 
 a notification.
 
 .. code-block:: shell

source/administration/monitoring/publish-events-to-mqtt.rst

@@ -194,7 +194,7 @@ the associated MQTT deployment as a target.
 1) Configure Bucket Notifications using the MQTT Endpoint as a Target
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Use the :mc-cmd:`mc event add` command to add a new bucket notification 
+Use the :mc:`mc event add` command to add a new bucket notification 
 event with the configured MQTT service as a target:
 
 .. code-block:: shell
@@ -209,7 +209,7 @@ event with the configured MQTT service as a target:
 - Replace ``EVENTS`` with a comma-separated list of :ref:`events 
   <mc-event-supported-events>` for which MinIO triggers notifications.
 
-Use :mc-cmd:`mc event list` to view all configured bucket events for 
+Use :mc:`mc event list` to view all configured bucket events for 
 a given notification target:
 
 .. code-block:: shell
@@ -227,7 +227,7 @@ when configuring the bucket notification.
 
 For example, if the bucket notification configuration includes the 
 ``s3:ObjectCreated:Put`` event, you can use the 
-:mc-cmd:`mc cp` command to create a new object in the bucket and trigger 
+:mc:`mc cp` command to create a new object in the bucket and trigger 
 a notification.
 
 .. code-block:: shell
@@ -360,7 +360,7 @@ specified when configuring the bucket notification.
 
 For example, if the bucket notification configuration includes the 
 ``s3:ObjectCreated:Put`` event, you can use the 
-:mc-cmd:`mc cp` command to create a new object in the bucket and trigger 
+:mc:`mc cp` command to create a new object in the bucket and trigger 
 a notification.
 
 .. code-block:: shell

source/administration/monitoring/publish-events-to-mysql.rst

@@ -181,7 +181,7 @@ the associated MySQL deployment as a target.
 3) Configure Bucket Notifications using the MySQL Endpoint as a Target
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Use the :mc-cmd:`mc event add` command to add a new bucket notification 
+Use the :mc:`mc event add` command to add a new bucket notification 
 event with the configured MySQL service as a target:
 
 .. code-block:: shell
@@ -196,7 +196,7 @@ event with the configured MySQL service as a target:
 - Replace ``EVENTS`` with a comma-separated list of :ref:`events 
   <mc-event-supported-events>` for which MinIO triggers notifications.
 
-Use :mc-cmd:`mc event list` to view all configured bucket events for 
+Use :mc:`mc event list` to view all configured bucket events for 
 a given notification target:
 
 .. code-block:: shell
@@ -214,7 +214,7 @@ when configuring the bucket notification.
 
 For example, if the bucket notification configuration includes the 
 ``s3:ObjectCreated:Put`` event, you can use the 
-:mc-cmd:`mc cp` command to create a new object in the bucket and trigger 
+:mc:`mc cp` command to create a new object in the bucket and trigger 
 a notification.
 
 .. code-block:: shell
@@ -333,7 +333,7 @@ specified when configuring the bucket notification.
 
 For example, if the bucket notification configuration includes the 
 ``s3:ObjectCreated:Put`` event, you can use the 
-:mc-cmd:`mc cp` command to create a new object in the bucket and trigger 
+:mc:`mc cp` command to create a new object in the bucket and trigger 
 a notification.
 
 .. code-block:: shell

source/administration/monitoring/publish-events-to-nats.rst

@@ -181,7 +181,7 @@ the associated NATS deployment as a target.
 3) Configure Bucket Notifications using the NATS Endpoint as a Target
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Use the :mc-cmd:`mc event add` command to add a new bucket notification 
+Use the :mc:`mc event add` command to add a new bucket notification 
 event with the configured NATS service as a target:
 
 .. code-block:: shell
@@ -196,7 +196,7 @@ event with the configured NATS service as a target:
 - Replace ``EVENTS`` with a comma-separated list of :ref:`events 
   <mc-event-supported-events>` for which MinIO triggers notifications.
 
-Use :mc-cmd:`mc event list` to view all configured bucket events for 
+Use :mc:`mc event list` to view all configured bucket events for 
 a given notification target:
 
 .. code-block:: shell
@@ -214,7 +214,7 @@ when configuring the bucket notification.
 
 For example, if the bucket notification configuration includes the 
 ``s3:ObjectCreated:Put`` event, you can use the 
-:mc-cmd:`mc cp` command to create a new object in the bucket and trigger 
+:mc:`mc cp` command to create a new object in the bucket and trigger 
 a notification.
 
 .. code-block:: shell
@@ -333,7 +333,7 @@ specified when configuring the bucket notification.
 
 For example, if the bucket notification configuration includes the 
 ``s3:ObjectCreated:Put`` event, you can use the 
-:mc-cmd:`mc cp` command to create a new object in the bucket and trigger 
+:mc:`mc cp` command to create a new object in the bucket and trigger 
 a notification.
 
 .. code-block:: shell

source/administration/monitoring/publish-events-to-nsq.rst

@@ -161,7 +161,7 @@ You must specify the ARN resource when configuring bucket notifications with the
 3) Configure Bucket Notifications using the NSQ Endpoint as a Target
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Use the :mc-cmd:`mc event add` command to add a new bucket notification event with the configured NSQ service as a target:
+Use the :mc:`mc event add` command to add a new bucket notification event with the configured NSQ service as a target:
 
 .. code-block:: shell
    :class: copyable
@@ -174,7 +174,7 @@ Use the :mc-cmd:`mc event add` command to add a new bucket notification event wi
 - Replace ``EVENTS`` with a comma-separated list of :ref:`events 
   <mc-event-supported-events>` for which MinIO triggers notifications.
 
-Use :mc-cmd:`mc event list` to view all configured bucket events for a given notification target:
+Use :mc:`mc event list` to view all configured bucket events for a given notification target:
 
 .. code-block:: shell
    :class: copyable
@@ -187,7 +187,7 @@ Use :mc-cmd:`mc event list` to view all configured bucket events for a given not
 Perform an action on the bucket for which you configured the new event and check the NSQ service for the notification data. 
 The action required depends on which :mc-cmd:`events <mc event add --event>` were specified when configuring the bucket notification.
 
-For example, if the bucket notification configuration includes the ``s3:ObjectCreated:Put`` event, you can use the :mc-cmd:`mc cp` command to create a new object in the bucket and trigger a notification.
+For example, if the bucket notification configuration includes the ``s3:ObjectCreated:Put`` event, you can use the :mc:`mc cp` command to create a new object in the bucket and trigger a notification.
 
 .. code-block:: shell
    :class: copyable
@@ -280,7 +280,7 @@ The :mc:`minio server` process prints a line on startup for each configured NSQ
 Perform an action on a bucket which has an event configuration using the updated NSQ service endpoint and check the NSQ service for the notification data. 
 The action required depends on which :mc-cmd:`events <mc event add --event>` were specified when configuring the bucket notification.
 
-For example, if the bucket notification configuration includes the ``s3:ObjectCreated:Put`` event, you can use the :mc-cmd:`mc cp` command to create a new object in the bucket and trigger a notification.
+For example, if the bucket notification configuration includes the ``s3:ObjectCreated:Put`` event, you can use the :mc:`mc cp` command to create a new object in the bucket and trigger a notification.
 
 .. code-block:: shell
    :class: copyable

source/administration/monitoring/publish-events-to-postgresql.rst

@@ -184,7 +184,7 @@ the associated PostgreSQL deployment as a target.
 3) Configure Bucket Notifications using the PostgreSQL Endpoint as a Target
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Use the :mc-cmd:`mc event add` command to add a new bucket notification 
+Use the :mc:`mc event add` command to add a new bucket notification 
 event with the configured PostgreSQL service as a target:
 
 .. code-block:: shell
@@ -198,7 +198,7 @@ event with the configured PostgreSQL service as a target:
 - Replace ``EVENTS`` with a comma-separated list of :ref:`events 
   <mc-event-supported-events>` for which MinIO triggers notifications.
 
-Use :mc-cmd:`mc event list` to view all configured bucket events for 
+Use :mc:`mc event list` to view all configured bucket events for 
 a given notification target:
 
 .. code-block:: shell
@@ -216,7 +216,7 @@ when configuring the bucket notification.
 
 For example, if the bucket notification configuration includes the 
 ``s3:ObjectCreated:Put`` event, you can use the 
-:mc-cmd:`mc cp` command to create a new object in the bucket and trigger 
+:mc:`mc cp` command to create a new object in the bucket and trigger 
 a notification.
 
 .. code-block:: shell
@@ -337,7 +337,7 @@ specified when configuring the bucket notification.
 
 For example, if the bucket notification configuration includes the 
 ``s3:ObjectCreated:Put`` event, you can use the 
-:mc-cmd:`mc cp` command to create a new object in the bucket and trigger 
+:mc:`mc cp` command to create a new object in the bucket and trigger 
 a notification.
 
 .. code-block:: shell

source/administration/monitoring/publish-events-to-redis.rst

@@ -164,7 +164,7 @@ the associated Redis deployment as a target.
 3) Configure Bucket Notifications using the Redis Endpoint as a Target
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Use the :mc-cmd:`mc event add` command to add a new bucket notification 
+Use the :mc:`mc event add` command to add a new bucket notification 
 event with the configured Redis service as a target:
 
 .. code-block:: shell
@@ -179,7 +179,7 @@ event with the configured Redis service as a target:
 - Replace ``EVENTS`` with a comma-separated list of :ref:`events 
   <mc-event-supported-events>` for which MinIO triggers notifications.
 
-Use :mc-cmd:`mc event list` to view all configured bucket events for 
+Use :mc:`mc event list` to view all configured bucket events for 
 a given notification target:
 
 .. code-block:: shell
@@ -197,7 +197,7 @@ when configuring the bucket notification.
 
 For example, if the bucket notification configuration includes the 
 ``s3:ObjectCreated:Put`` event, you can use the 
-:mc-cmd:`mc cp` command to create a new object in the bucket and trigger 
+:mc:`mc cp` command to create a new object in the bucket and trigger 
 a notification.
 
 .. code-block:: shell
@@ -306,7 +306,7 @@ specified when configuring the bucket notification.
 
 For example, if the bucket notification configuration includes the 
 ``s3:ObjectCreated:Put`` event, you can use the 
-:mc-cmd:`mc cp` command to create a new object in the bucket and trigger 
+:mc:`mc cp` command to create a new object in the bucket and trigger 
 a notification.
 
 .. code-block:: shell

source/administration/monitoring/publish-events-to-webhook.rst

@@ -162,7 +162,7 @@ the associated Webhook deployment as a target.
 3) Configure Bucket Notifications using the Webhook Endpoint as a Target
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Use the :mc-cmd:`mc event add` command to add a new bucket notification 
+Use the :mc:`mc event add` command to add a new bucket notification 
 event with the configured Webhook service as a target:
 
 .. code-block:: shell
@@ -177,7 +177,7 @@ event with the configured Webhook service as a target:
 - Replace ``EVENTS`` with a comma-separated list of :ref:`events 
   <mc-event-supported-events>` for which MinIO triggers notifications.
 
-Use :mc-cmd:`mc event list` to view all configured bucket events for 
+Use :mc:`mc event list` to view all configured bucket events for 
 a given notification target:
 
 .. code-block:: shell
@@ -195,7 +195,7 @@ when configuring the bucket notification.
 
 For example, if the bucket notification configuration includes the 
 ``s3:ObjectCreated:Put`` event, you can use the 
-:mc-cmd:`mc cp` command to create a new object in the bucket and trigger 
+:mc:`mc cp` command to create a new object in the bucket and trigger 
 a notification.
 
 .. code-block:: shell
@@ -304,7 +304,7 @@ were specified when configuring the bucket notification.
 
 For example, if the bucket notification configuration includes the 
 ``s3:ObjectCreated:Put`` event, you can use the 
-:mc-cmd:`mc cp` command to create a new object in the bucket and trigger 
+:mc:`mc cp` command to create a new object in the bucket and trigger 
 a notification.
 
 .. code-block:: shell