Merge remote-tracking branch 'upstream/master' into alerting-ui-tests-for-status-filters

# Please enter a commit message to explain why this merge is necessary,
# especially if it merges an updated upstream into a topic branch.
#
# Lines starting with '#' will be ignored, and an empty message aborts
# the commit.

Author: YulNaumenko

docs/api/dashboard/export-dashboard.asciidoc

@@ -11,6 +11,8 @@ experimental[] Export dashboards and corresponding saved objects.
 
 `GET <kibana host>:<port>/api/kibana/dashboards/export`
 
+`GET <kibana host>:<port>/s/<space-id>/api/kibana/dashboards/export`
+
 [[dashboard-api-export-params]]
 ==== Query parameters
 

docs/api/dashboard/import-dashboard.asciidoc

@@ -11,6 +11,8 @@ experimental[] Import dashboards and corresponding saved objects.
 
 `POST <kibana host>:<port>/api/kibana/dashboards/import`
 
+`POST <kibana host>:<port>/s/<space-id>/api/kibana/dashboards/import`
+
 [[dashboard-api-import-params]]
 ==== Query parameters
 

docs/apm/images/advanced-discover.png

@@ -157,7 +157,7 @@ the values in `http.request.cookies` are not indexed and thus not searchable.
 
 *Ensure an index pattern exists*
 As a first step, you should ensure the correct index pattern exists.
-In Kibana, navigate to *Management > Kibana > Index Patterns*.
+Open the main menu, then click *Stack Management > Index Patterns*.
 In the pattern list, you should see an apm index pattern; The default is `apm-*`.
 If you don't, the index pattern doesn't exist. See <<no-apm-data-found>> for information on how to fix this problem.
 

docs/apm/troubleshooting.asciidoc

@@ -14,7 +14,7 @@ For this tutorial, you'll need to add the <<add-sample-data, Sample eCommerce or
 
 Your first step to working with Canvas is to create a workpad.
 
-. Open the menu, then go to *Canvas*.
+. Open the main menu, then click *Canvas*.
 
 . On the *Canvas workpads* page, click *Create workpad*.
 

docs/canvas/canvas-tutorial.asciidoc

@@ -7,7 +7,7 @@ Console enables you to interact with the REST API of {es}. You can:
 * View API documentation
 * Get your request history
 
-To get started, open the menu, go to *Dev Tools*, then click *Console*.
+To get started, open the main menu, click *Dev Tools*, then click *Console*.
 
 [role="screenshot"]
 image::dev-tools/console/images/console.png["Console"]

docs/dev-tools/console/console.asciidoc

@@ -35,7 +35,7 @@ is automatically enabled in {kib}.
 NOTE: If you're using {stack-security-features}, you must have the `manage_pipeline`
 permission to use the Grok Debugger.
 
-. Open the menu, go to *Dev Tools*, then click *Grok Debugger*.
+. Open the main menu, click *Dev Tools*, then click *Grok Debugger*.
 . In *Sample Data*, enter a message that is representative of the data that you
 want to parse. For example:
 +

docs/dev-tools/grokdebugger/index.asciidoc

@@ -12,6 +12,6 @@ process {ref}/docs-reindex.html[reindexed data], define complex
 <<watcher-create-advanced-watch, Watcher conditions>>,
 and work with data in other contexts.
 
-To get started, open the menu, go to *Dev Tools*, then click *Painless Lab*.
+To get started, open the main menu, click *Dev Tools*, then click *Painless Lab*.
 
 image::dev-tools/painlesslab/images/painless-lab.png[Painless Lab]

docs/dev-tools/painlesslab/index.asciidoc

@@ -2,7 +2,7 @@
 [[profiler-getting-started]]
 === Getting Started
 
-The {searchprofiler} is automatically enabled in {kib}. From the menu, go to *Dev Tools*, then click *Search Profiler*
+The {searchprofiler} is automatically enabled in {kib}. Open the main menu, click *Dev Tools*, then click *Search Profiler*
 to get started.
 
 {searchprofiler} displays the names of the indices searched, the shards in each index,