[DOCS] Updates for navigation redesign (#68709) (#69027)

* [DOCS] Updates for navigation redesign

* Getting started

* Set up text

* Discover

* Dashboard, Graph, ML, Maps, APM, SIEM, Dev tools

* Dev Tools, Stack Monitoring, Management

* Management

* Final changes

* [DOCS] Updates for navigation redesign

* [DOCS] Updates CCR monitoring screenshots

* updates SIEM screenshot and Cases overview text

* Added Brandon's APM image

* [DOCS] Refines CCR shard screenshot

* Removed merge conflict image file

Co-authored-by: lcawl <lcawley@elastic.co>
Co-authored-by: Ben Skelker <ben.skelker@elastic.co>
# Conflicts:
#	docs/images/management-upgrade-assistant-9.0.png
#	docs/management/upgrade-assistant/index.asciidoc

docs/apm/machine-learning.asciidoc

@@ -1,6 +1,6 @@
 [role="xpack"]
 [[machine-learning-integration]]
-=== Machine Learning integration
+===  integration
 
 ++++
 <titleabbrev>Integrate with machine learning</titleabbrev>

docs/apm/transactions.asciidoc

@@ -64,7 +64,7 @@ The transaction overview page is customized for the JavaScript RUM Agent.
 This page highlights things like *page load times*, *transactions per minute*, and even the *average page load duration distribution by country*.
 
 [role="screenshot"]
-image::apm/images/apm-geo-ui.jpg[average page load duration distribution]
+image::apm/images/apm-geo-ui.png[average page load duration distribution]
 
 This data is available due to the geo-ip and user agent pipelines being enabled by default,
 which allows for the capture of geo-location and user agent data.

docs/canvas/canvas-tutorial.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 click *Kibana > Canvas*.
+. Open the menu, then go to *Canvas*.
 
 . On the *Canvas workpads* page, click *Create workpad*.
 

docs/canvas/canvas-workpad.asciidoc

@@ -20,7 +20,9 @@ To create a workpad, choose one of the following options:
 
 To use the background colors, images, and data of your choice, start with a blank workpad.
 
-. On the *Canvas workpads* page, click *Create workpad*.
+. Open the menu, then go to *Canvas*.
+
+. On the *Canvas workpads* view, click *Create workpad*.
 
 . Add a *Name* to your workpad.
 
@@ -41,7 +43,9 @@ image::images/canvas-background-color-picker.png[Canvas color picker]
 
 If you're unsure about where to start, you can use one of the preconfigured templates that come with Canvas.
 
-. On the *Canvas workpads* page, select *Templates*.
+. Open the menu, then go to *Canvas*.
+
+. On the *Canvas workpads* view, select *Templates*.
 
 . Click the preconfigured template that you want to use.
 
@@ -53,7 +57,9 @@ If you're unsure about where to start, you can use one of the preconfigured temp
 
 When you want to use a workpad that someone else has already started, import the JSON file into Canvas.
 
-To import a workpad, go to the *Canvas workpads* page, then click and drag the file to the *Import workpad JSON file* field.
+. Open the menu, then go to *Canvas*.
+
+. On the *Canvas workpads* view, click and drag the file to the *Import workpad JSON file* field.
 
 [float]
 [[sample-data-workpad]]

docs/dev-tools/console/console.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, go to *Dev Tools > Console*.
+To get started, open the menu, go to *Dev Tools*, then click *Console*.
 
 [role="screenshot"]
 image::dev-tools/console/images/console.png["Console"]

docs/dev-tools/grokdebugger/index.asciidoc

@@ -35,7 +35,7 @@ is automatically enabled in {kib}.
 NOTE: If you're using {security}, you must have the `manage_pipeline`
 permission to use the Grok Debugger.
 
-. In the side navigation, click *DevTools*, then open the *Grok Debugger*. 
+. Open the menu, go to *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/painlesslab/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, go to *Dev Tools > Painless Lab*.
+To get started, open the menu, go to *Dev Tools*, then click *Painless Lab*.
 
 image::dev-tools/painlesslab/images/painless-lab.png[Painless Lab]

docs/dev-tools/searchprofiler/getting-started.asciidoc

@@ -2,7 +2,7 @@
 [[profiler-getting-started]]
 === Getting Started
 
-The {searchprofiler} is automatically enabled in {kib}.  Go to *Dev Tools > Search Profiler*
+The {searchprofiler} is automatically enabled in {kib}. From the menu, go to *Dev Tools*, then click *Search Profiler*
 to get started.
 
 {searchprofiler} displays the names of the indices searched, the shards in each index,
@@ -11,10 +11,10 @@ with the query you want to profile and click *Profile*.
 
 The following example shows the results of profiling the `match_all` query.
 If we take a closer look at the information for the `.kibana_1` sample index, the
-Cumulative Time field shows us that the query took 0.067ms to execute.
+Cumulative Time field shows us that the query took 1.279ms to execute.
 
 [role="screenshot"]
-image::dev-tools/searchprofiler/images/query.png["{searchprofiler} example"]
+image::dev-tools/searchprofiler/images/overview.png["{searchprofiler} example"]
 
 
 [NOTE]

docs/discover/search.asciidoc

@@ -104,7 +104,9 @@ To save the current search:
 . Click *Save* in the Kibana toolbar.
 . Enter a name for the search and click *Save*.
 
-You can import, export and delete saved searches from *Management/Kibana/Saved Objects*.
+To import, export and delete saved searches:
+. Open the menu, then click *Stack Management.
+. From the {kib} menu, click *Saved Ojbects*.
 
 ==== Open a saved search
 To load a saved search into Discover:

docs/getting-started/tutorial-dashboard.asciidoc

@@ -1,17 +1,18 @@
 [[tutorial-dashboard]]
-=== Add visualizations to a dashboard
+=== Add the visualizations to a dashboard
 
-A dashboard is a collection of visualizations that you can arrange and share.
-You'll build a dashboard that contains the visualizations and map that you saved during
+Build a dashboard that contains the visualizations and map that you saved during
 this tutorial.
 
-. Open *Dashboard*.
-. On the Dashboard overview page, click *Create new dashboard*.
+. Open the menu, go to *Dashboard*, then click *Create dashboard*.
 . Set the time filter to May 18, 2015 to May 20, 2015.
-. Click *Add* in the menu bar.
-. Add *Bar Example*, *Map Example*, *Markdown Example*, and *Pie Example*.
+. Click *Add*, then select the following:
+ * *Bar Example*
+ * *Map Example*
+ * *Markdown Example*
+ * *Pie Example*
 +
-Your sample dashboard should look like this:
+Your sample dashboard looks like this:
 +
 [role="screenshot"]
 image::images/tutorial-dashboard.png[]
@@ -32,27 +33,21 @@ but sometimes you need to look at the actual data to
 understand what's really going on. You can inspect the data behind any visualization
 and view the {es} query used to retrieve it.
 
-. In the dashboard, hover the pointer over the pie chart, and then click the icon in the upper right.
-. From the *Options* menu, select *Inspect*.
+. Click the pie chart *Options* menu, then select *Inspect*.
 +
 [role="screenshot"]
 image::images/tutorial-full-inspect1.png[]
 
-. To look at the query used to fetch the data for the visualization, select *View > Requests*
-in the upper right of the Inspect pane.
+. To look at the query used to fetch the data for the visualization, select *View > Requests*.
 
 [float]
 === Next steps
 
-Now that you have a handle on the basics, you're ready to start exploring
-your own data with Kibana.
+Now that you have the basics, you're ready to start exploring
+your own data with {kib}.
 
-* See {kibana-ref}/discover.html[Discover] for information about searching and filtering
-your data.
-* See {kibana-ref}/visualize.html[Visualize] for information about the visualization
-types Kibana has to offer.
-* See {kibana-ref}/management.html[Management] for information about configuring Kibana
-and managing your saved objects.
-* See {kibana-ref}/console-kibana.html[Console] to learn about the interactive
-console you can use to submit REST requests to Elasticsearch.
+* To learn about searching and filtering your data, refer to {kibana-ref}/discover.html[Discover].
+* To learn about the visualization types {kib} has to offer, refer to {kibana-ref}/visualize.html[Visualize].
+* To learn about configuring {kib} and managing your saved objects, refer to {kibana-ref}/management.html[Management].
+* To learn about the interactive console you can use to submit REST requests to {es}, refer to {kibana-ref}/console-kibana.html[Console].
 

docs/getting-started/tutorial-define-index.asciidoc

@@ -18,35 +18,35 @@ First you'll create index patterns for the Shakespeare data set, which has an
 index named `shakespeare,` and the accounts data set, which has an index named
 `bank`. These data sets don't contain time series data.
 
-. In Kibana, open *Management*, and then click *Index Patterns.*
-. If this is your first index pattern, the *Create index pattern* page opens automatically.
+. Open the menu, then go to *Stack Management > {kib} > Index Patterns*.
+. If this is your first index pattern, the *Create index pattern* page opens.
 Otherwise, click *Create index pattern*.
-. Enter `shakes*` in the *Index pattern* field.
+. In the *Index pattern field*, enter `shakes*`.
 +
 [role="screenshot"]
 image::images/tutorial-pattern-1.png[]
 
 . Click *Next step*.
-. In *Configure settings*, click *Create index pattern*.
+. Select the *Time Filter field name*, then click *Create index pattern*.
 +
 You’re presented a table of all fields and associated data types in the index.
 
-. Return to the *Index patterns* overview page and define a second index pattern named  `ba*`. 
+. Return to the *Index patterns* page and create a second index pattern named  `ba*`. 
 
 [float]
-==== Create an index pattern for time series data
+==== Create an index pattern for the time series data
 
-Now create an index pattern for the Logstash index, which
-contains time series data.
+Create an index pattern for the Logstash index, which
+contains the time series data.
 
 . Define an index pattern named `logstash*`.
 . Click *Next step*.
-. Open the *Time Filter field name* dropdown and select *@timestamp*.
+. From the *Time Filter field name* dropdown, select *@timestamp*.
 . Click *Create index pattern*.
 
 NOTE: When you define an index pattern, the indices that match that pattern must
 exist in Elasticsearch and they must contain data. To check which indices are
-available, go to *Dev Tools > Console* and enter `GET _cat/indices`.  Alternately, use
+available, open the menu, then go to *Dev Tools > Console* and enter `GET _cat/indices`.  Alternately, use
 `curl -XGET "http://localhost:9200/_cat/indices"`.
 
 

docs/getting-started/tutorial-discovering.asciidoc

@@ -5,15 +5,15 @@ Using *Discover*, enter
 an {ref}/query-dsl-query-string-query.html#query-string-syntax[Elasticsearch
 query] to search your data and filter the results.
 
-. Open *Discover*.
+. Open the menu, then go to *Discover*.
 +
 The `shakes*` index pattern appears.
 
-. To make `ba*` the current index, click the index pattern dropdown, then select `ba*`.
+. To make `ba*` the index, click the *Change Index Pattern* dropdown, then select `ba*`.
 +
 By default, all fields are shown for each matching document.
 
-. In the search field, enter:
+. In the *Search* field, enter the following:
 +
 [source,text]
 account_number<100 AND balance>47500
@@ -25,7 +25,7 @@ excess of 47,500. Results appear for account numbers 8, 32, 78, 85, and 97.
 image::images/tutorial-discover-2.png[]
 
 . Hover over the list of *Available fields*, then
-click *add* next to each field you want include as a column in the table.
+click *Add* next to each field you want include in the table.
 +
 For example, when you add the `account_number` field, the display changes to a list of five
 account numbers.

docs/getting-started/tutorial-full-experience.asciidoc

@@ -94,7 +94,7 @@ You must also have the `create`, `manage` `read`, `write,` and `delete`
 index privileges. See {ref}/security-privileges.html[Security privileges] 
 for more information.
 
-In Kibana *Dev Tools > Console*, set up a mapping for the Shakespeare data set:
+Open *Dev Tools*. On the *Console* page, set up a mapping for the Shakespeare data set:
 
 [source,js]
 PUT /shakespeare

docs/getting-started/tutorial-sample-data.asciidoc

@@ -21,7 +21,7 @@ on the `kibana_sample_data_*` indices. See
 
 Install the Flights sample data set, if you haven't already.
 
-. On the {kib} home page, click the link underneath *Add sample data*. 
+. On the home page, click *Load a data set and a {kib} dashboard*. 
 . On the *Sample flight data* card, click *Add data*.
 . Once the data is added, click *View data > Dashboard*.
 +
@@ -29,7 +29,7 @@ You’re taken to the *Global Flight* dashboard, a collection of charts, graphs,
 maps, and other visualizations of the the data in the `kibana_sample_data_flights` index.
 +
 [role="screenshot"]
-image::images/tutorial-sample-dashboard.png[]
+image::getting-started/images/tutorial-sample-dashboard.png[]
 
 [float]
 [[tutorial-sample-filter]]
@@ -43,19 +43,19 @@ For more detailed information on these actions, see
 [float]
 ==== Filter the data
 
-. In the *Controls* visualization, set an *Origin City* and a *Destination City*.
+. In the *Controls* visualization, select an *Origin City* and a *Destination City*.
 . Click *Apply changes*.
 +
-The `OriginCityName` and the `DestCityName` fields are filtered to match 
+The `OriginCityName` and the `DestCityName` fields filter the data on the dasbhoard to match 
 the data you specified. 
 +
-For example, this dashboard shows the data for flights from London to Oslo. 
+For example, the following dashboard shows the data for flights from London to Milan. 
 +
 [role="screenshot"]
-image::images/tutorial-sample-filter.png[]
+image::getting-started/images/tutorial-sample-filter.png[]
 
-. To add a filter manually, click *Add filter* in the filter bar,
-and specify the data you want to view.
+. To add a filter manually, click *Add filter*,
+then specify the data you want to view.
 
 . When you are finished experimenting, remove all filters.
 
@@ -78,7 +78,7 @@ The dashboard updates to show data for the flights out of Rome on JetBeats and
 {kib} Airlines.  
 +
 [role="screenshot"]
-image::images/tutorial-sample-query.png[]
+image::getting-started/images/tutorial-sample-query.png[]
 
 . When you are finished exploring the dashboard, remove the query by 
 clearing the contents in the query bar and clicking *Update*.
@@ -92,7 +92,7 @@ matches the selected index pattern. The index pattern tells {kib} which {es} ind
 exploring. You can submit search queries, filter the 
 search results, and view document data.
 
-. In the side navigation, click *Discover*.
+. From the menu, click *Discover*.
 
 . Ensure `kibana_sample_data_flights` is the current index pattern. 
 You might need to click *New* in the menu bar to refresh the data.
@@ -102,7 +102,7 @@ documents over time. A table lists the fields for
 each matching document. By default, all fields are shown.
 +
 [role="screenshot"]
-image::images/tutorial-sample-discover1.png[]
+image::getting-started/images/tutorial-sample-discover1.png[]
 
 . To choose which fields to display, 
 hover the pointer over the list of *Available fields*, and then click *add* next 
@@ -112,7 +112,7 @@ For example, if you add the `DestAirportID` and `DestWeather` fields,
 the display includes columns for those two fields.
 +
 [role="screenshot"]
-image::images/tutorial-sample-discover2.png[]
+image::getting-started/images/tutorial-sample-discover2.png[]
 
 [float]
 [[tutorial-sample-edit]]
@@ -146,7 +146,7 @@ categories, or buckets.
 You now see the average ticket price for all four airlines.
 +
 [role="screenshot"]
-image::images/tutorial-sample-edit1.png[]
+image::getting-started/images/tutorial-sample-edit1.png[]
 
 [float]
 ==== Save the visualization
@@ -160,7 +160,7 @@ handle in the lower right. You can also rearrange the visualizations by clicking
 the header and dragging. Be sure to save the dashboard.
 +
 [role="screenshot"]
-image::images/tutorial-sample-edit2.png[]
+image::getting-started/images/tutorial-sample-edit2.png[]
 
 [float]
 [[tutorial-sample-inspect]]
@@ -177,7 +177,7 @@ and view the {es} query used to retrieve it.
 The initial view shows the document count. 
 +
 [role="screenshot"]
-image::images/tutorial-sample-inspect1.png[]
+image::getting-started/images/tutorial-sample-inspect1.png[]
 
 . To look at the query used to fetch the data for the visualization, select *View > Requests*
 in the upper right of the Inspect pane.

docs/getting-started/tutorial-visualizing.asciidoc

@@ -1,7 +1,7 @@
 [[tutorial-visualizing]]
 === Visualize your data
 
-In the Visualize application, you can shape your data using a variety
+In *Visualize*, you can shape your data using a variety
 of charts, tables, and maps, and more. In this tutorial, you'll create four
 visualizations:
 
@@ -14,21 +14,20 @@ visualizations:
 [[tutorial-visualize-pie]]
 === Pie chart
 
-You'll use the pie chart to
+Use the pie chart to
 gain insight into the account balances in the bank account data.
 
-. Open *Visualize* to show the overview page.
-. Click *Create new visualization*. You'll see all the visualization
-types in Kibana.
+. Open then menu, then go to *Visualize*.
+. Click *Create visualization*.
 +
 [role="screenshot"]
 image::images/tutorial-visualize-wizard-step-1.png[]
 . Click *Pie*.
 
-. In *Choose a source*, select the `ba*` index pattern.
+. On the *Choose a source* window, select `ba*`.
 +
 Initially, the pie contains a single "slice."
-That's because the default search matched all documents.
+That's because the default search matches all documents.
 +
 To specify which slices to display in the pie, you use an Elasticsearch
 {ref}/search-aggregations.html[bucket aggregation]. This aggregation
@@ -39,8 +38,8 @@ each range.
 
 . In the *Buckets* pane, click *Add > Split slices.*
 +
-.. In the *Aggregation* dropdown, select *Range*.
-.. In the *Field* dropdown, select *balance*.
+.. From the *Aggregation* dropdown, select *Range*.
+.. From the *Field* dropdown, select *balance*.
 .. Click *Add range* four times to bring the total number of ranges to six.
 .. Define the following ranges:
 +
@@ -52,7 +51,7 @@ each range.
 15000       30999
 31000       50000
 
-. Click *Apply changes* image:images/apply-changes-button.png[].
+. Click *Update*.
 +
 Now you can see what proportion of the 1000 accounts fall into each balance
 range.
@@ -63,56 +62,54 @@ image::images/tutorial-visualize-pie-2.png[]
 . Add another bucket aggregation that looks at the ages of the account
 holders.
 
-.. At the bottom of the *Buckets* pane, click *Add*.
-.. For *sub-bucket type,* select *Split slices*.
-.. In the *Sub aggregation* dropdown, select *Terms*.
-.. In the *Field* dropdown, select *age*.
+.. In the *Buckets* pane, click *Add*, then click *Split slices*.
+.. From the *Sub aggregation* dropdown, select *Terms*.
+.. From the *Field* dropdown, select *age*.
 
-. Click  *Apply changes* image:images/apply-changes-button.png[].
+. Click  *Update*.
 +
-Now you can see the break down of the ages of the account holders, displayed
+The break down of the ages of the account holders are displayed
 in a ring around the balance ranges.
 +
 [role="screenshot"]
 image::images/tutorial-visualize-pie-3.png[]
 
-. To save this chart so you can use it later, click *Save* in
-the top menu bar and enter `Pie Example`.
+. Click *Save*, then enter `Pie Example` in the *Title* field.
 
 [float]
 [[tutorial-visualize-bar]]
 === Bar chart
 
-You'll use a bar chart to look at the Shakespeare data set and compare
+Use a bar chart to look at the Shakespeare data set and compare
 the number of speaking parts in the plays.
 
-. Create a *Vertical Bar* chart and set the search source to `shakes*`.
+. Click *Create visualization > Vertical Bar*, then set the source to `shakes*`.
 +
 Initially, the chart is a single bar that shows the total count
 of documents that match the default wildcard query.
 
-. Show the number of speaking parts per play along the Y-axis.
+. Show the number of speaking parts per play along the y-axis.
 
 .. In the *Metrics* pane, expand *Y-axis*.
-.. Set *Aggregation* to *Unique Count*.
-.. Set *Field* to *speaker*.
-.. In the *Custom label* box, enter `Speaking Parts`.
+.. From the *Aggregation* dropdown, select *Unique Count*.
+.. From the *Field* dropdown, select *speaker*.
+.. In the *Custom label* field, enter `Speaking Parts`.
 
-. Click  *Apply changes* image:images/apply-changes-button.png[].
+. Click *Update*.
 
-. Show the plays along the X-axis.
+. Show the plays along the x-axis.
 
 .. In the *Buckets* pane, click *Add > X-axis*.
-.. Set *Aggregation* to *Terms*.
-.. Set *Field* to *play_name*.
-.. To list plays alphabetically, in the *Order* dropdown, select *Ascending*.
-.. Give the axis a custom label, `Play Name`.
+.. From the *Aggregation* dropdown, select *Terms*.
+.. From the *Field* dropdown, select *play_name*.
+.. To list the plays alphabetically, select *Ascending* from the *Order* dropdown.
+.. In the *Custom label* field, enter `Play Name`.
 
-. Click  *Apply changes* image:images/apply-changes-button.png[].
+. Click *Update*.
 +
 [role="screenshot"]
 image::images/tutorial-visualize-bar-1.5.png[]
-. *Save* this chart with the name `Bar Example`.
+. *Save* the chart with the name `Bar Example`.
 +
 Hovering over a bar shows a tooltip with the number of speaking parts for
 that play.
@@ -126,24 +123,24 @@ as `not analyzed`.
 [[tutorial-visualize-markdown]]
 === Markdown
 
-Create a Markdown widget to add formatted text to your dashboard.
+Add formatted text to your dashboard with a markdown tool.
 
-. Create a *Markdown* visualization.
-. Copy the following text into the text box.
+. Click *Create visualization > Markdown*.
+. In the text field, enter the following:
 +
 [source,markdown]
 # This is a tutorial dashboard!
 The Markdown widget uses **markdown** syntax.
 > Blockquotes in Markdown use the > character.
 
-. Click *Apply changes* image:images/apply-changes-button.png[].
+. Click *Update*.
 +
 The Markdown renders in the preview pane.
 +
 [role="screenshot"]
 image::images/tutorial-visualize-md-2.png[]
 
-. *Save* this visualization with the name `Markdown Example`.
+. *Save* the tool with the name `Markdown Example`.
 
 [float]
 [[tutorial-visualize-map]]
@@ -151,34 +148,32 @@ image::images/tutorial-visualize-md-2.png[]
 
 Using <<maps>>, you can visualize geographic information in the log file sample data.
 
-. Click *Maps* in the New Visualization
-menu to create a Map.
+. Click *Create visualization > Maps*.
 
 . Set the time.
 .. In the time filter, click *Show dates*.
 .. Click the start date, then *Absolute*.
 .. Set the *Start date* to May 18, 2015.
-.. In the time filter, click *now*, then *Absolute*.
+.. Click *now*, then *Absolute*.
 .. Set the *End date* to May 20, 2015.
 .. Click *Update*
 
 . Map the geo coordinates from the log files.
 
+.. Click *Add layer > Clusters and Grids*.
+.. From the *Index pattern* dropdown, select *logstash*.
 .. Click *Add layer*.
-.. Click the *Grid aggregation* data source.
-.. Set *Index pattern* to *logstash*.
-.. Click the *Add layer* button.
 
-. Set the layer style.
-.. For *Fill color*, select the yellow to red color ramp.
-.. For *Border color*, select white.
+. Set the *Layer Style*.
+.. From the *Fill color* dropdown, select the yellow to red color ramp.
+.. From the *Border color* dropdown, select white.
 .. Click *Save & close*.
 +
-The map now looks like this:
+The map looks like this:
 +
 [role="screenshot"]
 image::images/tutorial-visualize-map-2.png[]
 
 . Navigate the map by clicking and dragging.  Use the controls
 to zoom the map and set filters.
-. *Save* this map with the name `Map Example`.
+. *Save* the map with the name `Map Example`.

docs/management/advanced-options.asciidoc

@@ -5,7 +5,7 @@ The *Advanced Settings* UI enables you to edit settings that control the behavio
 For example, you can change the format used to display dates, specify the default index pattern, and set the precision
 for displayed decimal values.
 
-. Go to *Management > {kib} > Advanced Settings*.
+. Open the menu, then go to *Stack Management > {kib} > Advanced Settings*.
 . Scroll or search for the setting you want to modify.
 . Enter a new value for the setting.
 . Click *Save changes*.

docs/management/alerting/alerts-and-actions-intro.asciidoc

@@ -6,7 +6,7 @@ beta[]
 
 The *Alerts and Actions* UI lets you <<alert-management, see and control all the alerts>> in a space, and provides tools to <<connector-management, create and manage connectors>> so that alerts can trigger actions like notification, indexing, and ticketing. 
 
-To manage alerting and connectors, go to *Management > {kib} > Alerts and Actions*.
+To manage alerting and connectors, open the menu, then go to *Stack Management > {kib} > Alerts and Actions*.
 
 [role="screenshot"]
 image:management/alerting/images/alerts-and-actions-ui.png[Example alert listing in the Alerts and Actions UI]

docs/management/index-lifecycle-policies/add-policy-to-index.asciidoc

@@ -2,15 +2,15 @@
 [[adding-policy-to-index]]
 === Adding a policy to an index
 
-You can add a lifecycle policy to an index and view the status for indices 
-managed by a policy in *Management > {es} > Index Management*.  This page lists your 
+To add a lifecycle policy to an index and view the status for indices 
+managed by a policy, open the menu, then go to *Stack Management > {es} > Index Management*.  This page lists your 
 {es} indices, which you can filter by lifecycle status and lifecycle phase.  
 
-To add a policy, select the index name and then select *Manage > Add lifecycle policy*.
+To add a policy, select the index name and then select *Manage Index > Add lifecycle policy*.
 You’ll see the policy name, the phase the index is in, the current 
 action, and if any errors occurred performing that action. 
 
-To remove a policy from an index, select *Manage > Remove lifecycle policy*.
+To remove a policy from an index, select *Manage Index > Remove lifecycle policy*.
 
 [role="screenshot"]
 image::images/index_management_add_policy.png[][UI for adding a policy to an index]

docs/management/index-lifecycle-policies/create-policy.asciidoc

@@ -12,8 +12,8 @@ you’re likely moving your data to less performant hardware and reducing the
 number of shards and replicas.  It’s important to ensure that the index 
 continues to have enough replicas to prevent data loss in the event of failures.
 
-*Index Lifecycle Policies* is automatically enabled in {kib}. Go to 
-*Management > {es} > Index Lifecycle Policies*. 
+*Index Lifecycle Policies* is automatically enabled in {kib}. Open the menu, then go to 
+*Stack Management > {es} > Index Lifecycle Policies*. 
 
 NOTE: If you don’t want to use this feature, you can disable it by setting 
 `xpack.ilm.enabled` to false in your `kibana.yml` configuration file. If you 

docs/management/index-lifecycle-policies/example-index-lifecycle-policy.asciidoc

@@ -59,7 +59,7 @@ output as described in {filebeat-ref}/filebeat-getting-started.html[Getting Star
 {filebeat} includes a default {ilm-init} policy that enables rollover. {ilm-init}
 is enabled automatically if you’re using the default `filebeat.yml` and index template.
 
-To view the default policy in {kib}, go to *Management > Index Lifecycle Policies*,
+To view the default policy in {kib}, open the menu, go to * Stack Management > {es} > Index Lifecycle Policies*,
 search for _filebeat_, and choose the _filebeat-version_ policy.
 
 This policy initiates the rollover action when the index size reaches 50GB or
@@ -114,8 +114,8 @@ If meeting a specific retention time period is most important, you can create a
 custom policy.  For this option, you will use {filebeat} daily indices without
 rollover.
 
-. Create a custom policy in {kib}, go to *Management > Index Lifecycle Policies >
-Create Policy*.
+. To create a custom policy, open the menu, go to *Stack Management > {es} > Index Lifecycle Policies*, then click 
+*Create policy*.
 
 . Activate the warm phase and configure it as follows:
 +
@@ -156,8 +156,8 @@ image::images/tutorial-ilm-custom-policy.png["Modify the custom policy to add a
 [role="screenshot"]
 image::images/tutorial-ilm-delete-phase-creation.png["Delete phase"]
 
-. Configure the index to use the new policy in *{kib} > Management > Index Lifecycle
-Policies*
+. To configure the index to use the new policy, open the menu, then go to *Stack Management > {es} > Index Lifecycle
+Policies*.
 
 .. Find your {ilm-init} policy.
 .. Click the *Actions* link next to your policy name.

docs/management/index-patterns.asciidoc

@@ -25,9 +25,8 @@ image::images/management-index-read-only-badge.png[Example of Index Pattern Mana
 [[settings-create-pattern]]
 === Create an index pattern
 
-If you are in an app that requires an index pattern, and you don't have one yet,
-{kib} prompts you to create one.  Or, you can go directly to
-*Management > Kibana > Index Patterns*.
+When you don't have an index pattern, {kib} prompts you to create one. Or, you can open the menu, 
+then go to *Stack Management > {kib} > Index Patterns* to go directly to the *Index Patterns* UI.
 
 [role="screenshot"]
 image:management/index-patterns/images/rollup-index-pattern.png["Menu with rollup index pattern"]

docs/management/managing-beats.asciidoc

@@ -4,7 +4,7 @@
 
 include::{asciidoc-dir}/../../shared/discontinued.asciidoc[tag=cm-discontinued]
 
-Use the Central Management UI under *Management > {beats}* to define and
+To use the Central Management UI, open the menu, go to *Stack Management > {beats} > Central Management*, then define and
 manage configurations in a central location in {kib} and quickly deploy
 configuration changes to all {beats} running across your enterprise. For more
 about central management, see the related {beats} documentation:
@@ -17,8 +17,8 @@ about central management, see the related {beats} documentation:
 This feature requires an Elastic license that includes {beats} central
 management.
 
-Don't have a license? You can start a 30-day trial. In {kib}, go to
-*Management > License Management*. At the end of the trial
+Don't have a license? You can start a 30-day trial. Open the menu, go to
+*Stack Management > Elasticsearch > License Management*. At the end of the trial
 period, you can purchase a subscription to keep using central management. For
 more information, see https://www.elastic.co/subscriptions and
 {stack-ov}/license-management.html[License Management].

docs/management/managing-ccr.asciidoc

@@ -7,7 +7,7 @@ remote clusters on a local cluster. {ref}/xpack-ccr.html[Cross-cluster replicati
 is commonly used to provide remote backups for disaster recovery and for
 geo-proximite copies of data.
 
-To get started, go to *Management > Cross-Cluster Replication*.
+To get started, open the menu, then go to *Stack Management > Elasticsearch > Cross-Cluster Replication*.
 
 [role="screenshot"]
 image::images/cross-cluster-replication-list-view.png[][Cross-cluster replication list view]

docs/management/managing-fields.asciidoc

@@ -134,7 +134,7 @@ https://www.elastic.co/blog/using-painless-kibana-scripted-fields[Using Painless
 [[create-scripted-field]]
 === Create a scripted field
 
-. Go to *Management > {kib} > Index Patterns*
+. Open the menu, then go to *Stack Management > {kib} > Index Patterns*
 . Select the index pattern you want to add a scripted field to.
 . Go to the *Scripted fields* tab for the index pattern, then click *Add scripted field*.
 . Enter a name for the scripted field.
@@ -148,7 +148,6 @@ For more information about scripted fields in {es}, see
 [[update-scripted-field]]
 === Update a scripted field
 
-. Go to *Management > {kib} > Index Patterns*
 . Click the *Scripted fields* tab for the index pattern.
 . Click the *Edit* button for the scripted field you want to change.
 . Make your changes, then click *Save field*.
@@ -160,7 +159,6 @@ exceptions whenever you try to view the dynamically generated data.
 [[delete-scripted-field]]
 === Delete a scripted field
 
-. Go to *Management > {kib} > Index Patterns*
 . Click the *Scripted fields* tab for the index pattern.
 . Click *Delete* for the scripted field you want to remove.
 . Click *Delete* on the confirmation window.

docs/management/managing-indices.asciidoc

@@ -13,7 +13,7 @@ the amount of bookkeeping when working with indices. Instead of manually
 setting up your indices, you can create them automatically from a template,
 ensuring that your settings, mappings, and aliases are consistently defined.
 
-To manage your indices, go to *Management > {es} > Index Management*.
+To manage your indices, open the menu, then go to *Stack Management > {es} > Index Management*.
 
 [role="screenshot"]
 image::images/management_index_labels.png[Index Management UI]

docs/management/managing-licenses.asciidoc

@@ -6,8 +6,8 @@ with no expiration date. For the full list of free features that are included in
 the basic license, refer to https://www.elastic.co/subscriptions[the subscription page].
 
 If you want to try out the full set of platinum features, you can activate a
-30-day trial license. Go to *Management > License Management* to view the
-status of your license, start a trial, or install a new license.
+30-day trial license. To view the
+status of your license, start a trial, or install a new license, open the menu, then go to *Stack Management > {es} > License Management*.
 
 NOTE: You can start a trial only if your cluster has not already activated a
 trial license for the current major product version. For example, if you have
@@ -15,7 +15,7 @@ already activated a trial for 6.0, you cannot start a new trial until
 7.0. You can, however, contact `info@elastic.co` to request an extended trial
 license.
 
-When you activate a new license level, new features appear in *Management*.
+When you activate a new license level, new features appear in *Stack Management*.
 
 [role="screenshot"]
 image::images/management-license.png[]

docs/management/managing-remote-clusters.asciidoc

@@ -6,7 +6,7 @@ connection from your cluster to other clusters. This functionality is
 required for {ref}/xpack-ccr.html[cross-cluster replication] and
 {ref}/modules-cross-cluster-search.html[cross-cluster search].
 
-To get started, go to *Management > Remote Clusters*.
+To get started, open the menu, then go to *Stack Management > {es} > Remote Clusters*.
 
 [role="screenshot"]
 image::images/remote-clusters-list-view.png[Remote Clusters list view, including Add a remote cluster button]

docs/management/managing-saved-objects.asciidoc

@@ -5,7 +5,7 @@ The *Saved Objects* UI helps you keep track of and manage your saved objects. Th
 store data for later use, including dashboards, visualizations, maps, index patterns,
 Canvas workpads, and more.
 
-To get started, go to *Management > {kib} > Saved Objects*. With this UI, you can:
+To get started, open the menu, then go to *Stack Management > {kib} > Saved Objects*. With this UI, you can:
 
 * <<managing-saved-objects-view, View&#44; edit&#44; and delete saved objects>>
 * <<managing-saved-objects-export-objects, Import and export saved objects>>
@@ -62,7 +62,7 @@ the NDJSON includes related objects. Exported dashboards include their associate
 [float]
 [role="xpack"]
 [[managing-saved-objects-copy-to-space]]
-=== [xpack]#Copy to other {kib} spaces#
+=== Copy to other {kib} spaces
 
 To copy a saved object to another space, click the actions icon image:images/actions_icon.png[Actions icon]
 and select *Copy to space*. From here, you can select the spaces in which to copy the object.

docs/management/rollups/create_and_manage_rollups.asciidoc

@@ -8,7 +8,7 @@ by an index pattern, and then rolls it into a new index. Rollup indices are a go
 compactly store months or years of historical
 data for use in visualizations and reports.
 
-You’ll find *Rollup Jobs* under *Management > Elasticsearch*. With this UI,
+To get started, open the menu, then go to *Stack Management > {es} > Rollup Jobs*. With this UI,
 you can:
 
 * <<create-and-manage-rollup-job, Create a rollup job>>

docs/management/snapshot-restore/index.asciidoc

@@ -8,7 +8,7 @@ Snapshots are important because they provide a copy of your data in case
 something goes wrong. If you need to roll back to an older version of your data,
 you can restore a snapshot from the repository.
 
-You’ll find *Snapshot and Restore* under *Management > Elasticsearch*.
+To get started, open the menu, then go to *Stack Management > {es} > Snapshot and Restore*.
 With this UI, you can:
 
 * Register a repository for storing your snapshots
@@ -32,7 +32,7 @@ The minimum required permissions to access *Snapshot and Restore* include:
 * Cluster privileges: `monitor`, `manage_slm`, `cluster:admin/snapshot`, and `cluster:admin/repository`
 * Index privileges: `all` on the `monitor` index if you want to access content in the *Restore Status* tab
 
-You can add these privileges in *Management > Security > Roles*.
+To add privileges, open the menu, then go to *Stack Management > Security > Roles*.
 
 [role="screenshot"]
 image:management/snapshot-restore/images/snapshot_permissions.png["Edit Role"]
@@ -191,7 +191,7 @@ your master and data nodes.  You can do this in one of two ways:
 Use *Snapshot and Restore* to register the repository where your snapshots
 will live.
 
-. Go to *Management > Elasticsearch > Snapshot and Restore*.
+. Open the menu, then go to *Stack Management > {es} > Snapshot and Restore*.
 . Click *Register a repository* in either the introductory message or *Repository view*.
 . Enter a name for your repository, for example, `my_backup`.
 . Select *Shared file system*.
@@ -212,7 +212,7 @@ The repository currently doesn’t have any snapshots.
 ==== Add a snapshot to the repository
 Use the {ref}/snapshots-take-snapshot.html[snapshot API] to create a snapshot.
 
-. Go to *Dev Tools > Console*.
+. Open the menu, go to *Dev Tools*, then select *Console*.
 . Create the snapshot:
 +
 [source,js]

docs/management/upgrade-assistant/index.asciidoc

@@ -2,48 +2,48 @@
 [[upgrade-assistant]]
 == Upgrade Assistant
 
-The Upgrade Assistant helps you prepare for your upgrade to {es} 8.0. 
-To access the assistant, go to *Management > 8.0 Upgrade Assistant*. 
+The Upgrade Assistant helps you prepare for your upgrade to {es} 9.0.
+To access the assistant, open the menu, then go to *Stack Management > {es} > 9.0 Upgrade Assistant*.
 
-The assistant identifies the deprecated settings in your cluster and indices 
-and guides you through the process of resolving issues, including reindexing. 
+The assistant identifies the deprecated settings in your cluster and indices
+and guides you through the process of resolving issues, including reindexing.
 
-Before upgrading to Elasticsearch 8.0, make sure that you are using the final 
-7.x minor release to see the most up-to-date deprecation issues. 
+Before upgrading to Elasticsearch 8.0, make sure that you are using the final
+7.x minor release to see the most up-to-date deprecation issues.
 
 [float]
 === Reindexing
 
-The *Indices* page lists the indices that are incompatible with the next 
+The *Indices* page lists the indices that are incompatible with the next
 major version of {es}. You can initiate a reindex to resolve the issues.
 
 [role="screenshot"]
 image::images/management-upgrade-assistant-8.0.png[]
 
-For a preview of how the data will change during the reindex, select the 
-index name. A warning appears if the index requires destructive changes.  
-Back up your index, then proceed with the reindex by accepting each breaking change.  
+For a preview of how the data will change during the reindex, select the
+index name. A warning appears if the index requires destructive changes.
+Back up your index, then proceed with the reindex by accepting each breaking change.
 
-You can follow the progress as the Upgrade Assistant makes the index read-only, 
-creates a new index, reindexes the documents, and creates an alias that points 
-from the old index to the new one. 
+You can follow the progress as the Upgrade Assistant makes the index read-only,
+creates a new index, reindexes the documents, and creates an alias that points
+from the old index to the new one.
 
-If the reindexing fails or is cancelled, the changes are rolled back, 
-the new index is deleted, and the original index becomes writable. An error 
+If the reindexing fails or is cancelled, the changes are rolled back,
+the new index is deleted, and the original index becomes writable. An error
 message explains the reason for the failure.
 
-You can reindex multiple indices at a time, but keep an eye on the 
-{es} metrics, including CPU usage, memory pressure, and disk usage. If a metric 
-is so high it affects query performance, cancel the reindex and continue 
+You can reindex multiple indices at a time, but keep an eye on the
+{es} metrics, including CPU usage, memory pressure, and disk usage. If a metric
+is so high it affects query performance, cancel the reindex and continue
 by reindexing fewer indices at a time.
 
 Additional considerations:
 
 * If you use {alert-features}, when you reindex the internal indices
-(`.watches`), the {watcher} process pauses and no alerts are triggered.  
+(`.watches`), the {watcher} process pauses and no alerts are triggered.
 
 * If you use {ml-features}, when you reindex the internal indices (`.ml-state`),
-the {ml} jobs pause and models are not trained or updated. 
+the {ml} jobs pause and models are not trained or updated.
 
 * If you use {security-features}, before you reindex the internal indices
 (`.security*`), it is a good idea to create a temporary superuser account in the

docs/management/watcher-ui/index.asciidoc

@@ -8,7 +8,7 @@ Watches are helpful for analyzing mission-critical and business-critical
 streaming data. For example, you might watch application logs for performance
 outages or audit access logs for security threats.
 
-To get started with the Watcher UI, go to *Management > Elasticsearch > Watcher*.
+To get started with the Watcher UI, open then menu, then go to *Stack Management > {es} > Watcher*.
 With this UI, you can:
 
 * <<watcher-create-threshold-alert, Create a simple threshold watch>>
@@ -40,7 +40,7 @@ and either of these watcher roles:
 * `watcher_admin`. You can perform all Watcher actions, including create and edit watches.
 * `watcher_user`. You can view watches, but not create or edit them.
 
-You can manage roles in *Management > Security > Roles*, or use the
+To manage roles, open then menu, then go to *Stack Management > Security > Roles*, or use the
 <<role-management-api, Kibana Role Management API>>. Watches are shared between
 all users with the same role.
 

docs/maps/geojson-upload.asciidoc

@@ -17,7 +17,7 @@ GeoJSON is the most commonly used and flexible option.
 Follow these instructions to upload a GeoJSON data file, or try the
 <<indexing-geojson-data-tutorial, end-to-end integrated example>>.
 
-. Open *Elastic Maps*, and then click *Add layer*.
+. Open the menu, go to *Elastic Maps*, and then click *Add layer*.
 . Click *Uploaded GeoJSON*.
 +
 [role="screenshot"]