move migration and event data content up one level (#4378)

* moved migration folder and updated links

* moved enrich data folder, updated links, and retitled index page

* updated sidebar order of sentry basics pages

* added redirects

* fixed link text

* fixed link text

Author: imatwawana

src/docs/product/discover-queries/uncover-trends.mdx

@@ -7,13 +7,13 @@ redirect_from:
 description: "Learn how to work with the data in Discover to gain useful insights into the health and stability of your applications."
 ---
 
-Discover is a powerful query engine that allows you to query all your error metadata across projects and applications. As you've probably noticed, the Sentry SDKs installed in your applications capture huge amounts of events, each enriched with contextual data about the underlying error, platform, device, user, and more. We also highly encourage enriching your error data through the SDK by adding custom tags and configuring the release and environment. For more information see [Put your Data to Work](/product/sentry-basics/guides/enrich-data/).
+Discover is a powerful query engine that allows you to query all your error metadata across projects and applications. As you've probably noticed, the Sentry SDKs installed in your applications capture huge amounts of events, each enriched with contextual data about the underlying error, platform, device, user, and more. We also highly encourage enriching your error data through the SDK by adding custom tags and configuring the release and environment. For more information see [Event Data](/product/sentry-basics/enrich-data/).
 
 Let's go over some examples of how to work with all this data to gain some useful insights into the health and stability of your applications.
 
 <Note>
 
-Some table column options may be repeated if you’ve set up a tag with the same name as a Sentry field. For the examples that follow, use the table column option marked “field.” 
+Some table column options may be repeated if you’ve set up a tag with the same name as a Sentry field. For the examples that follow, use the table column option marked “field.”
 
 </Note>
 
@@ -94,7 +94,7 @@ To find out which files in your codebase are generating the most errors, run the
 ![By File Names](010.png)
 
 Change your "Display" selection to compare the current period to the previous one.
- 
+
 You can continue exploring a specific filename by adding it to the filter and changing the table columns to display the major error culprits in that file:
 
 ![Culprits](008.png)

src/docs/product/sentry-basics/dsn-explainer.mdx

@@ -1,6 +1,6 @@
 ---
 title: Data Source Name (DSN)
-sidebar_order: 0
+sidebar_order: 10
 description: "Learn about Sentry's Data Source Name structure and use."
 ---
 

src/docs/product/sentry-basics/guides/enrich-data/001.png renamed to src/docs/product/sentry-basics/enrich-data/001.png

@@ -1,9 +1,10 @@
 ---
-title: Put Your Data to Work
-sidebar_order: 5
+title: Event Data
+sidebar_order: 60
 redirect_from:
   - /guides/enrich-data/
-description: "Learn how to configure Sentry workflows and tools to fine-tune the data sent to Sentry."
+  - /product/sentry-basics/guides/enrich-data/
+description: "Learn about event data and how to configure Sentry workflows and tools to fine-tune the data sent to Sentry."
 ---
 
 The Sentry SDK captures errors, exceptions, crashes, and generally anything that goes wrong in your application in real-time.

src/docs/product/sentry-basics/guides/enrich-data/002.png renamed to src/docs/product/sentry-basics/enrich-data/002.png

@@ -1,6 +1,6 @@
 ---
 title: Environments
-sidebar_order: 1
+sidebar_order: 20
 redirect_from:
   - /enriching-error-data/environments/
   - /learn/environments/