Update some info on distribution servers (#2119) (#2179)

* update some links

* remove galax details and leave it to galaxy docs

(cherry picked from commit 7f11306)

Co-authored-by: Sandra McCann <[email protected]>

Author: patchback[bot]

docs/docsite/rst/dev_guide/developing_collections_distributing.rst

@@ -53,7 +53,7 @@ You must upload your collection into a namespace on each distribution server. If
 You can create additional namespaces on Ansible Galaxy if you choose. For Red Hat Automation Hub and private Automation Hub you must create a namespace before you can upload your collection. To create a namespace:
 
 * To create a namespace on Galaxy, see `Galaxy namespaces <https://galaxy.ansible.com/docs/contributing/namespaces.html#galaxy-namespaces>`_ on the Galaxy docsite for details.
-* To create a namespace on Red Hat Automation Hub, see the `Ansible Certified Content FAQ <https://access.redhat.com/articles/4916901>`_.
+* To create a namespace on Red Hat Automation Hub, see the `Red Hat automation content documentation <https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/>`_.
 
 Specify the namespace in the :file:`galaxy.yml` file for each collection. For more information on the :file:`galaxy.yml` file, see :ref:`collections_galaxy_meta`.
 
@@ -66,8 +66,8 @@ An API token authenticates your connection to each distribution server. You need
 
 To get your API token:
 
-* To get an API token for Galaxy, go to the `Galaxy profile preferences <https://galaxy.ansible.com/me/preferences>`_ page and click :guilabel:`API Key`.
-* To get an API token for Automation Hub, go to `the token page <https://cloud.redhat.com/ansible/automation-hub/token/>`_ and click :guilabel:`Load token`.
+* To get an API token for Galaxy, see `the Galaxy documentation <https://galaxy.ansible.com/ui/token/>`_.
+* To get an API token for Automation Hub, see the  `Red Hat automation content documentation <https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/>`_.
 
 .. _galaxy_specify_token:
 
@@ -385,14 +385,8 @@ The ``ansible-galaxy collection publish`` command triggers an import process, ju
 Publishing a collection from the website
 ----------------------------------------
 
-To publish your collection directly on the Galaxy website:
+See the `Galaxy documentation <https://ansible.readthedocs.io/projects/galaxy-ng/en/latest/usage_guide/collections/#via-the-ui>`_ to learn how to publish your collection directly on the Galaxy website.
 
-#. Go to the `My Content <https://galaxy.ansible.com/my-content/namespaces>`_ page, and click the **Add Content** button on one of your namespaces.
-#. From the **Add Content** dialog, click **Upload New Collection**, and select the collection archive file from your local filesystem.
-
-When you upload a collection, Ansible always uploads the tarball to the namespace specified in the collection metadata in the ``galaxy.yml`` file, no matter which namespace you select on the website. If you are not an owner of the namespace specified in your collection metadata, the upload request fails.
-
-After Galaxy uploads and accepts a collection, the website shows you the **My Imports** page. This page shows import process information. You can review any errors or warnings about your upload there.
 
 .. seealso::