[DOCS] fix a couple of typos

[lonlylocly]

Hello,

This pull request is to fix a couple of typos I spotted in the documentation.

Please tell me if there is any problem with it.

I also tried to run the docs-related checks but didn't succeed:

$ ./gradlew -p docs check

> Task :docs:integTestCluster#wait FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':docs:integTestCluster#wait'.
> Failed to start elasticsearch: timed out after 30 seconds

...

BUILD FAILED in 5m 42s
364 actionable tasks: 77 executed, 287 up-to-date

Thank you.

[cbuescher]

@lonlylocly Thanks for your contribution and for taking the time to help improve our documentations. These are all great catches, I will merge them soon.

Also thanks for trying to run the docs checks. I don't think they are necessary for this kind of change that doesn't change any code snippets, but I will start a full CI run anyway before merging. If you are intereted in further info about testing an building our docs please let me know, happy to help.

[cbuescher]

@elasticmachine test this please

[lonlylocly]

@cbuescher Thank you! Yes, I also thought that for a typo in the docs tests might not be necessary.

I will give the build another try, since I'd like to contribute to the code in the future, maybe there is a way to increase the timeout (my laptop is 3 years old and it just never happens on other developers' machines).

I suppose this is the line that times out (./docs/build.gradle:79):

  73 project.rootProject.subprojects.findAll { it.parent.path == ':plugins' }.each { subproj ->
  74   /* Skip repositories. We just aren't going to be able to test them so it
  75    * doesn't make sense to waste time installing them. */
  76   if (subproj.path.startsWith(':plugins:repository-')) {
  77     return
  78   }
  79   subproj.afterEvaluate { // need to wait until the project has been configured
  80     integTestCluster {
  81       plugin subproj.path
  82     }
  83   }

If you have any idea why this might be timing out please tell.

Thanks!

[cbuescher]

@lonlylocly thanks, your changes should be on the master, 6.5 and 6.4 branches of the documentation soon.

maybe there is a way to increase the timeout (my laptop is 3 years old and it just never happens on other developers' machines)

Execution failed for task ':docs:integTestCluster#wait'.
> Failed to start elasticsearch: timed out after 30 seconds

This means the test framework is trying to start a small test cluster that it uses internally, and this didn't come up as expected. My first guess would be not enough resources, maybe memory or CPU is low. There are some logs written to docs/build/integTestCluster\ node[xxx]/elasticsearch-[version]/logs that might give you more info about why the cluster couldn't start, but I'm not sure its easy to debug.

I just ran ./gradlew -p docs check on my machine and it terminated at about 7 min, but this is a beefy new laptop. I must admit the tests use a lot of resources.

I will give the build another try, since I'd like to contribute to the code in the future

Sounds great, always welcome. In case you are interested in more work on the docs (which is a good start), there is https://github.com/elastic/docs that contains our tools for building the documentation or parts of it which comes with a good README. It might be slightly out of date in some places, but should be a good place to start in case you want to make bigger changes to the docs and want to test them.

[lonlylocly]

Thanks! I checked out the logs and nothing suspicious there. Will return to this if I will happen to make another contribution.

UPDATE. Succeeded on a different, bigger machine, on the second try! :)