Apply suggestions from code review

Co-authored-by: Quentin Pradet <[email protected]>

Author: szabosteve

README.md

@@ -19,7 +19,7 @@ This JSON representation is formally defined by [a set of TypeScript definitions
 that also explains the various properties and their values.
 
 > [!TIP]
-> To learn more about how to write docs specifically for our [API references](https://www.elastic.co/docs/api/), refer to our [contribution guide](https://www.elastic.co/docs/extend/contribute/api-docs/).
+> To learn more about how to write docs specifically for our [API references](https://www.elastic.co/docs/api/), refer to the [Contribute to Elastic API docs](https://www.elastic.co/docs/extend/contribute/api-docs/).
 
 ## Prepare the environment
 

docs/add-new-api.md

@@ -6,7 +6,7 @@ but we don't have a type definition for it.
 In this document you will see how to add a new endpoint and how to add a new endpoint definition.
 
 > [!TIP]
-> To learn more about how to write docs specifically for our [API references](https://www.elastic.co/docs/api/), refer to our [contribution guide](https://www.elastic.co/docs/extend/contribute/api-docs/).
+> To learn more about how to write docs specifically for our [API references](https://www.elastic.co/docs/api/), refer to the [Contribute to Elastic API docs](https://www.elastic.co/docs/extend/contribute/api-docs/).
 
 ## How to add a new endpoint
 

docs/doc-comments-guide.md

@@ -5,7 +5,7 @@ A specification is not only about formalizing data structures, it's also about e
 Documentation of the TypeScript specification is made using [JSDoc](https://jsdoc.app/) comments, i.e. multiline comments starting with `/**` above a type or field declaration.
 
 The first phrase is used as the mandatory operation summary in the OpenAPI document.
-Refer to the [API docs contribution guidelines](https://www.elastic.co/docs/extend/contribute/api-docs/guidelines) to learn more about how to create great documentation for your API.
+Refer to the [Elastic API docs contribution guidelines](https://www.elastic.co/docs/extend/contribute/api-docs/guidelines) to learn more about how to create great documentation for your API.
 
 > [!NOTE] 
 > You must add a period at the end of the phrase for it to parse correctly. The period will be properly omitted from the output OpenAPI document.
@@ -76,7 +76,7 @@ GFM also has implementations in most languages, meaning that code generators wil
 
 ## Structuring a doc-comment
 
-For guidelines of how to write great doc-comments, refer to the [Contribute to API docs](https://www.elastic.co/docs/extend/contribute/api-docs/guidelines#write-descriptions) page.
+For guidelines of how to write great doc-comments, refer to the [Contribute to Elastic API docs](https://www.elastic.co/docs/extend/contribute/api-docs/guidelines#write-descriptions) page.
 
 ### Terseness
 

docs/schema-structure.md

@@ -13,7 +13,7 @@ Refer to the [documentation guide](doc-comments-guide.md) to add documentation t
 and to the [modeling guide](modeling-guide.md) to learn how to model the different types.
 
 > [!TIP]
-> To learn more about how to write docs specifically for our [API references](https://www.elastic.co/docs/api/), refer to our [contribution guide](https://www.elastic.co/docs/extend/contribute/api-docs/).
+> To learn more about how to write docs specifically for our [API references](https://www.elastic.co/docs/api/), refer to the [Contribute to Elastic API docs](https://www.elastic.co/docs/extend/contribute/api-docs/).
 
 You can find the schema representing all APIs and types in the [output folder](output/schema/schema.json).
 The schema is structured as follows: