Fix Typo "using using" in RLIKE/LIKE docs

[nicpenning]

Might fix #133891 ?

[elasticsearchmachine]

Pinging @elastic/es-analytical-engine (Team:Analytics)

[nik9000]

This is almost the right place. We generate these docs by running our tests. So running the tests will undo this. If you do this:

--- a/x-pack/plugin/esql/src/main/java/org/elasticsearch/xpack/esql/expression/function/scalar/string/regex/RLike.java
+++ b/x-pack/plugin/esql/src/main/java/org/elasticsearch/xpack/esql/expression/function/scalar/string/regex/RLike.java
@@ -32,7 +32,7 @@ public class RLike extends RegexMatch<RLikePattern> {
     public static final String NAME = "RLIKE";
 
     @FunctionInfo(returnType = "boolean", description = """
-        Use `RLIKE` to filter data based on string patterns using using
+        Use `RLIKE` to filter data based on string patterns using
         <<regexp-syntax,regular expressions>>. `RLIKE` usually acts on a field placed on

Then run:

./gradlew :x-pack:plugin:esql:test -Dtests.class='*RLikeTests'

That'll regenerate all those md and json files we pass around. It needs to run the tests, but should be fine. A lot of the docs generation stuff is linked into the tests because we generate tables and stuff from the test inputs.

Would you like to make those changes on this PR? I'd be happy to merge it.

[nik9000]

The story is that both kibana and the docs build need stuff about esql function. And the place with the most comprehensive list of supported parameter combinations is our docs. So we had the tests generate the json and markdown files kibana and the docs need. It's a bit of a pain to rerun the tests but it's a lot less painful than hand maintaining a bunch of files. We commit the generated markdown and json files because the docs build and kibana build don't know anything about how to run Elaticsearch's build. It's certainly not ideal that these can get out of date. But it's the compromise we chose to keep the docs and kibana builds simpler.

[nicpenning]

Please go ahead and resolve as you see fit. I appreciate the back end info as I may give another run at this another time. If this is in the contributor docs somewhere and I missed it, please send me a link! If not, no worries I will use these methods next time.

[elasticsearchmachine]

Pinging @elastic/core-docs (Team:Docs)

[nik9000]

Looks like I was wrong. This bit isn't generated. But other bits are. I'll catch the other bits up in a follow up change and merge this.

[github-actions]

ℹ️ Important: Docs version tagging

👋 Thanks for updating the docs! Just a friendly reminder that our docs are now cumulative. This means all 9.x versions are documented on the same page and published off of the main branch, instead of creating separate pages for each minor version.

We use applies_to tags to mark version-specific features and changes.

Expand for a quick overview

When to use applies_to tags:

✅ At the page level to indicate which products/deployments the content applies to (mandatory)
✅ When features change state (e.g. preview, ga) in a specific version
✅ When availability differs across deployments and environments

What NOT to do:

❌ Don't remove or replace information that applies to an older version
❌ Don't add new information that applies to a specific version without an applies_to tag
❌ Don't forget that applies_to tags can be used at the page, section, and inline level

🤔 Need help?

• Check out the cumulative docs guidelines
• Reach out in the #docs Slack channel

[nik9000]

I opened #134138 to cover the other bits.

[leemthompo]

thx @nicpenning and @nik9000!

[nik9000]

Thanks again @nicpenning .

[nicpenning]

No problem! Happy to help (or try to :)).