[james-project] 22/26: JAMES-3771 Examples: Elastic => OpenSearch rewords

[bt...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

btellier pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/james-project.git

commit b4876cb5d91d0d5b42808614af9f514b182989c1
Author: Benoit Tellier <bt...@linagora.com>
AuthorDate: Mon Aug 8 10:20:02 2022 +0700

    JAMES-3771 Examples: Elastic => OpenSearch rewords
---
 examples/README.md                  | 2 +-
 examples/oidc/james/jmap.properties | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/examples/README.md b/examples/README.md
index 6066851875..83e6dccd4b 100644
--- a/examples/README.md
+++ b/examples/README.md
@@ -22,7 +22,7 @@ components to achieve basic logic. But what if our goals are more complex? What
 Mailbox Listener is a component in James Mailbox System. Each time an action is applied on a mailbox(adding, deleting),
  or on an email(adding, deleting, updating flags...), then an event representing that action is generated and delivered 
  to all the Listeners that had been registered before. After receiving events, listeners retrieve information from the 
- events then execute their business (Indexing emails in ElasticSearch, updating quota of users, detecting spam emails...)
+ events then execute their business (Indexing emails in OpenSearch, updating quota of users, detecting spam emails...)
  
 **Mailbox Listeners** allow customizing the behaviour of James used as a Mail Delivery Agent (MDA). 
 
diff --git a/examples/oidc/james/jmap.properties b/examples/oidc/james/jmap.properties
index 7ea63f2746..7903409f16 100644
--- a/examples/oidc/james/jmap.properties
+++ b/examples/oidc/james/jmap.properties
@@ -19,7 +19,7 @@ tls.secret=james72laBalle
 #
 #jwt.publickeypem.url=file://conf/jwt_publickey
 
-# Should simple Email/query be resolved against a Cassandra projection, or should we resolve them against ElasticSearch?
+# Should simple Email/query be resolved against a Cassandra projection, or should we resolve them against OpenSearch?
 # This enables a higher resilience, but the projection needs to be correctly populated. False by default.
 # view.email.query.enabled=true
 


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@james.apache.org
For additional commands, e-mail: notifications-help@james.apache.org