Skip to content

Commit

Permalink
Use attributes
Browse files Browse the repository at this point in the history
Co-authored-by: István Zoltán Szabó <[email protected]>
  • Loading branch information
leemthompo and szabosteve authored Aug 27, 2024
1 parent 3062ac9 commit 56cfb44
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 3 deletions.
4 changes: 2 additions & 2 deletions docs/reference/intro.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ Use {es} to search, index, store, and analyze data of all shapes and sizes in ne
{es} has a lot of features. Explore the full list on the https://www.elastic.co/elasticsearch/features[product webpage^].
====

{es} is the heart of the the <<elasticsearch-intro-elastic-stack,Elastic Stack>> and powers the Elastic https://www.elastic.co/enterprise-search[Search], https://www.elastic.co/observability[Observability] and https://www.elastic.co/security[Security] solutions.
{es} is the heart of the the <<elasticsearch-intro-elastic-stack,{stack}>> and powers the Elastic https://www.elastic.co/enterprise-search[Search], https://www.elastic.co/observability[Observability] and https://www.elastic.co/security[Security] solutions.

{es} is used for a wide and growing range of use cases. Here are a few examples:

Expand All @@ -18,7 +18,7 @@ Use {es} to search, index, store, and analyze data of all shapes and sizes in ne
* *Vector database*. Store and search vectorized data, create vector embeddings with built-in and third-party NLP models.
* *Retrieval augmented generation (RAG)*. Use {es} as a retrieval engine to augment Generative AI models.
* *Application and security monitoring*. Monitor and analyze application performance and security data effectively.
* *Machine learning*. Use machine learning to automatically model the behavior of your data in real time.
* *Machine learning*. Use {ml} to automatically model the behavior of your data in real-time.

This is just a sample of search, observability, and security use cases enabled by {es}.
Refer to our https://www.elastic.co/customers/success-stories[customer success stories] for concrete examples across a range of industry verticals.
Expand Down
2 changes: 1 addition & 1 deletion docs/reference/modules/shard-ops.asciidoc
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
[[shard-allocation-relocation-recovery]]
=== Shard allocation, relocation, and recovery

Each index in Elasticsearch is divided into one or more <<scalability,shards>>.
Each index in {es} is divided into one or more <<scalability,shards>>.
Each document in an index belongs to a single shard.

A cluster can contain multiple copies of a shard. Each shard has one distinguished shard copy called the _primary_, and zero or more non-primary copies called _replicas_. The primary shard copy serves as the main entry point for all indexing operations. The operations on the primary shard copy are then forwarded to its replicas.
Expand Down

0 comments on commit 56cfb44

Please sign in to comment.