[Docs] Fixed a couple of typos in CONTRIBUTING (#63205)
Fixed a couple of typos in contribution guide. (cherry picked from commit 71fcaa41d83bfc5388d22c9b07d2800ee19a8fe8)
This commit is contained in:
parent
19650e860a
commit
dab1b14a10
|
@ -126,7 +126,7 @@ specifically these lines tell you that Elasticsearch is ready:
|
|||
[2020-05-29T14:50:35,167][INFO ][o.e.h.AbstractHttpServerTransport] [runTask-0] publish_address {127.0.0.1:9200}, bound_addresses {[::1]:9200}, {127.0.0.1:9200}
|
||||
[2020-05-29T14:50:35,169][INFO ][o.e.n.Node ] [runTask-0] started
|
||||
|
||||
But to be honest its typically easier to wait until the console stopps scrolling
|
||||
But to be honest its typically easier to wait until the console stops scrolling
|
||||
and then run `curl` in another window like this:
|
||||
|
||||
curl -u elastic:password localhost:9200
|
||||
|
@ -415,13 +415,13 @@ allows you to use these configurations arbitrarily. Here are some of the most
|
|||
common configurations in our build and how we use them:
|
||||
|
||||
<dl>
|
||||
<dt>`implementation`</dt><dd>Dependencies that are used by the project
|
||||
<dt>`implementation`</dt><dd>Dependencies that are used by the project
|
||||
at compile and runtime but are not exposed as a compile dependency to other dependent projects.
|
||||
Dependencies added to the `implementation` configuration are considered an implementation detail
|
||||
Dependencies added to the `implementation` configuration are considered an implementation detail
|
||||
that can be changed at a later date without affecting any dependent projects.</dd>
|
||||
<dt>`api`</dt><dd>Dependencies that are used as compile and runtime depdendencies of a project
|
||||
<dt>`api`</dt><dd>Dependencies that are used as compile and runtime dependencies of a project
|
||||
and are considered part of the external api of the project.
|
||||
<dt>`runtimeOnly`</dt><dd>Dependencies that not on the classpath at compile time but
|
||||
<dt>`runtimeOnly`</dt><dd>Dependencies that not on the classpath at compile time but
|
||||
are on the classpath at runtime. We mostly use this configuration to make sure that
|
||||
we do not accidentally compile against dependencies of our dependencies also
|
||||
known as "transitive" dependencies".</dd>
|
||||
|
|
Loading…
Reference in New Issue