Skip to content

Commit 033b505

Browse files
minor improvements
1 parent 438df70 commit 033b505

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

explore-analyze/discover/background-search.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ Sometimes you might need to search through large amounts of data, no matter how
2121

2222
You can send your long-running searches to the background from **Discover** or **Dashboards** and let them run while you continue your work.
2323

24-
A notification appears when a background search has completed, and lets you open the list of background searches. You can also access that list at any time to check the status of your searches and interact with them from the {icon}`background_task` **Background searches** button in the toolbar.
24+
A notification appears when a background search has completed, and allows you to open the list of background searches. You can also access that list at any time to check the status of your searches and interact with them from the {icon}`background_task` **Background searches** button in the toolbar.
2525

2626
![Send search to background](https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/bltee31dcf0d3917c75/68ecf412e5bae49d65a286ff/background-search.gif " =75%")
2727

@@ -31,7 +31,7 @@ A notification appears when a background search has completed, and lets you open
3131
This feature is disabled by default. You can enable background searches in versions 9.2 and higher, or search sessions in versions 9.1 and lower, by setting [`data.search.sessions.enabled`](kibana://reference/configuration-reference/search-sessions-settings.md) to `true` in the [`kibana.yml`](/deploy-manage/stack-settings.md) configuration file.
3232

3333
:::{note} - Exception for search sessions users
34-
If you are upgrading to version 9.2 or higher and search sessions were already enabled before, background searches are already enabled.
34+
If you upgrade to version 9.2 or higher with search sessions enabled in the version you upgrade from, background searches are automatically enabled.
3535
:::
3636

3737
## Usage requirements [_requirements]
@@ -71,7 +71,7 @@ Background searches expire after 7 days. Beyond that period, you must run the se
7171

7272
## Reopen or manage background searches
7373

74-
From the list of background searches, you can reopen and edit any searches, but also extend their validity period or delete to keep only searches that you care about.
74+
From the list of background searches, you can reopen and edit any searches, but also extend their validity period or delete them to keep only searches that you care about.
7575

7676
1. Open your list of background searches using one of the following methods:
7777
- Once a background search has completed, a notification appears to inform you, with a link to open the list of background searches.

reference/glossary/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -75,7 +75,7 @@ $$$glossary-zone$$$ availability zone
7575
## B [b-glos]
7676

7777
$$$glossary-background-search$$$ Background search
78-
: A query executed asynchronously. The results of the background search are stored for a period of time, so you can access it once it has completed. Background searches are user specific. Before {{stack}} 9.2, background searches are called ["search sessions"](#glossary-search-session).
78+
: A long-running query queued and executed while you perform other tasks. The results of the background search are stored for a period of time, so you can access it once it has completed. Background searches are user specific. Before {{stack}} 9.2, background searches are called ["search sessions"](#glossary-search-session).
7979

8080
$$$glossary-basemap$$$ basemap
8181
: The background detail necessary to orient the location of a map.

0 commit comments

Comments
 (0)