update links to rasa x docs

CHANGELOG.rst

@@ -62,7 +62,7 @@ Bugfixes
 Bugfixes
 --------
 - `#5521 <https://github.com/rasahq/rasa/issues/5521>`_: Responses used in ResponseSelector now support new lines with explicitly adding ``\n`` between them.
-- `#5758 <https://github.com/rasahq/rasa/issues/5758>`_: Fixed a bug in `rasa export <https://rasa.com/docs/rasa-x/installation-and-setup/existing-deployment/#migrate-conversations>`_ (:ref:`section_export`) which caused Rasa Open Source to only migrate conversation events from the last :ref:`session_config`.
+- `#5758 <https://github.com/rasahq/rasa/issues/5758>`_: Fixed a bug in `rasa export <https://rasa.com/docs/rasa-x/installation-and-setup/deploy#connect-rasa-deployment>`_ (:ref:`section_export`) which caused Rasa Open Source to only migrate conversation events from the last :ref:`session_config`.
 
 
 [1.10.1] - 2020-05-15

docs/api/event-brokers.rst

@@ -10,7 +10,7 @@ Event Brokers
 
 An event broker allows you to connect your running assistant to other services that process the data coming 
 in from conversations. For example, you could `connect your live assistant to 
-Rasa X <https://rasa.com/docs/rasa-x/installation-and-setup/existing-deployment/>`_
+Rasa X <https://rasa.com/docs/rasa-x/installation-and-setup/deploy#connect-rasa-deployment/>`_
 to review and annotate conversations or forward messages to an external analytics
 service. The event broker publishes messages to a message streaming service, 
 also known as a message broker, to forward Rasa :ref:`events` from the Rasa server to other services.

docs/core/interactive-learning.rst

@@ -23,7 +23,7 @@ Some people call this `Software 2.0 <https://medium.com/@karpathy/software-2-0-a
 
     Rasa X provides a UI for interactive learning, and you can use any user conversation
     as a starting point. See
-    `Talking to Your Assistant <https://rasa.com/docs/rasa-x/user-guide/enable-workflows#talking-to-your-assistant/>`_
+    `Talk to Your Bot <https://rasa.com/docs/rasa-x/user-guide/share-assistant/#talk-to-your-bot>`_
     in the Rasa X docs.
 
 .. contents::

docs/core/reminders-and-external-events.rst

@@ -75,7 +75,7 @@ But here we want to make use of the fact that the reminder can carry entities, a
 
   Reminders currently (Rasa 1.8) don't work in `rasa shell`.
   You have to test them with a
-  `running Rasa X server <https://rasa.com/docs/rasa-x/installation-and-setup/docker-compose-script/>`_ instead.
+  `running Rasa X server <https://rasa.com/docs/rasa-x/installation-and-setup/installation-guide/>`_ instead.
 
 .. note::
 

docs/user-guide/building-assistants.rst

@@ -686,7 +686,8 @@ The decision to handle these types of user input should always come from reviewi
 real conversations. You should first build part of your assistant, test it with real users
 (whether that's your end user, or your colleague) and then add what's missing. You shouldn't
 try to implement every possible edge case that you think might happen, because in the end
-your users may never actually behave in that way. `Rasa X <https://rasa.com/docs/rasa-x/installation-and-setup/docker-compose-script/>`__
+your users may never actually behave in that way.
+`Rasa X <https://rasa.com/docs/rasa-x/>`__
 is a tool that can help you review conversations and make these types of decisions.
 
 Generic interjections

docs/user-guide/connectors/your-own-website.rst

@@ -9,7 +9,7 @@ Your Own Website
 
 If you just want an easy way for users to test your bot, the best option
 is usually the chat interface that ships with Rasa X, where you can `invite users
-to test your bot <https://rasa.com/docs/rasa-x/user-guide/enable-workflows/#conversations-with-test-users>`_.
+to test your bot <https://rasa.com/docs/rasa-x/user-guide/share-assistant/#share-your-bot>`_.
 
 If you already have an existing website and want to add a Rasa assistant to it,
 you can use `Chatroom <https://github.com/scalableminds/chatroom>`_, a widget which you can incorporate into your existing webpage by adding a HTML snippet.

docs/user-guide/how-to-deploy.rst

@@ -23,7 +23,7 @@ important happy paths or is what we call a `minimum viable assistant <https://ra
 
 The recommended deployment methods described below make it easy to share your assistant
 with test users via the `share your assistant feature in
-Rasa X <https://rasa.com/docs/rasa-x/user-guide/enable-workflows#conversations-with-test-users>`_.
+Rasa X <https://rasa.com/docs/rasa-x/user-guide/share-assistant/#share-your-bot>`_.
 Then, when you’re ready to make your assistant available via one or more :ref:`messaging-and-voice-channels`,
 you can easily add them to your existing deployment set up.
 

docs/user-guide/setting-up-ci-cd.rst

@@ -37,7 +37,7 @@ Continuous Integration (CI)
 ---------------------------
 
 The best way to improve an assistant is with frequent `incremental updates
-<https://rasa.com/docs/rasa-x/user-guide/improve-assistant/>`_.
+<https://rasa.com/docs/rasa-x/user-guide/fix-problems>`_.
 No matter how small a change is, you want to be sure that it doesn't introduce
 new problems or negatively impact the performance of your assistant.
 
@@ -110,7 +110,7 @@ End-to-end testing is only as thorough and accurate as the test
 cases you include, so you should continue to grow your set of test conversations
 as you make improvements to your assistant. A good rule of thumb to follow is that you should aim for your test conversations
 to be representative of the true distribution of real conversations.
-Rasa X makes it easy to `add test conversations based on real conversations <https://rasa.com/docs/rasa-x/user-guide/improve-assistant.html#add-test-conversation>`_.
+Rasa X makes it easy to `add test conversations based on real conversations <https://rasa.com/docs/rasa-x/user-guide/test-assistant/#how-to-create-tests>`_.
 
 Note: End-to-end testing does **not** execute your action code. You will need to
 :ref:`test your action code <testing-action-code>` in a seperate step.