Clarify remote cluster recommendation in "Configuring Elasticsearch" article

• Type: New Article
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 7.0.x, 7.1.x
• Component/s: Product Team Search
• Labels:
  • search_fc_22_04
• Type of Documentation: Deployment
• Git Pull Request: https://github.com/sez11a/liferay-docs/pull/4979

In these 2 articles:

https://help.liferay.com/hc/en-us/articles/360018175651

https://help.liferay.com/hc/en-us/articles/360018175971

we have this statement:

"By default, Elasticsearch runs as an embedded search engine, but it's only supported in production as a separate server or cluster. "

A customer interpreted this to mean that we don't support remote operation in non-prod environments. In other words "it is only supported in production", but not other purposes. 

The intention behind the statement is to say that in production, it is only supported as a separate cluster, and not supported if embedded.

I looked at other similar statements, that are clearer:

https://help.liferay.com/hc/en-us/articles/360029031631-Elasticsearch#embedded-vs-remote-operation-mode

• You wouldn't run an embedded database like HSQL in production, and you shouldn't run Elasticsearch in embedded mode in production either. Instead, run Elasticsearch in remote operation mode, as a standalone server or cluster of server nodes.

https://help.liferay.com/hc/en-us/articles/360017895852

• By default, Liferay DXP uses Elasticsearch as an embedded service. It works, but this is not a supported configuration for a production server. 

Can you please update the ones listed at the top to avoid future misunderstandings? It might be good to mention that a separate cluster is useful in a non-production environment, so the setup is closer to the prod environment.