Updates to checklist and worflows pages per Fab's review

- Reordered sections: moved "Structure, organization, and metadata" before "Content quality and completeness"
- Removed all checkboxes and converted to plain bullet points
- Added reference to quickstart guide for previewing
- Removed validation checklist item about OpenAPI document structure

- Changed navigation title from "Find your team's workflow" to "API docs by product"
- Updated heading from "Find the workflow for your API docs" to "How each Elastic product manages API docs"
- Shifted language from "team" to "product" terminology in descriptions

Author: leemthompo

extend/contribute/api-docs/checklist.md

@@ -6,30 +6,28 @@ navigation_title: Checklist
 
 Use this checklist to verify the quality, completeness, and consistency of your API docs contributions.
 
-## Content quality and completeness
-
+## Structure, organization, and metadata
+- Include required [OpenAPI document info](./organize-annotate.md#add-open-api-document-info)
+- Include [OpenAPI specification version](./organize-annotate.md#add-openapi-specification-version)
+- Define unique [operation identifiers](./organize-annotate.md#add-operation-identifiers) using camelCase
+- Use consistent [tags](./organize-annotate.md#group-apis-with-tags) to group related operations
+- Document [API lifecycle status](./organize-annotate.md#specify-api-lifecycle-status) (availability, stability, version information)
+- Mark deprecated APIs and properties with appropriate notices
+- Document [required permissions](./organize-annotate.md#document-required-permissions) for each operation
 
-- ☑️ Write clear [summaries](./guidelines.md#write-summaries) (30 characters max, start with a verb)
-- ☑️ Write detailed [descriptions](./guidelines.md#write-descriptions) for operations, parameters, properties, tags etc.
-- ☑️ Document all [path parameters](./guidelines.md#document-path-parameters) with constraints and formats
-- ☑️ Provide descriptions for non-obvious [enum values](./guidelines.md#document-enum-values)
-- ☑️ Specify [default values](./guidelines.md#set-default-values) for optional parameters
-- ☑️ Include realistic [examples](./guidelines.md#add-examples) with helpful descriptions
-- ☑️ Add [links](./guidelines.md#add-links) to related operations and documentation
+## Content quality and completeness
 
-## Structure, organization, and metadata
-- ☑️ Include required [OpenAPI document info](./organize-annotate.md#add-open-api-document-info)
-- ☑️ Include [OpenAPI specification version](./organize-annotate.md#add-openapi-specification-version)
-- ☑️ Define unique [operation identifiers](./organize-annotate.md#add-operation-identifiers) using camelCase
-- ☑️ Use consistent [tags](./organize-annotate.md#group-apis-with-tags) to group related operations
-- ☑️ Document [API lifecycle status](./organize-annotate.md#specify-api-lifecycle-status) (availability, stability, version information)
-- ☑️ Mark deprecated APIs and properties with appropriate notices
-- ☑️ Document [required permissions](./organize-annotate.md#document-required-permissions) for each operation
+- Write clear [summaries](./guidelines.md#write-summaries) (30 characters max, start with a verb)
+- Write detailed [descriptions](./guidelines.md#write-descriptions) for operations, parameters, properties, tags etc.
+- Document all [path parameters](./guidelines.md#document-path-parameters) with constraints and formats
+- Provide descriptions for non-obvious [enum values](./guidelines.md#document-enum-values)
+- Specify [default values](./guidelines.md#set-default-values) for optional parameters
+- Include realistic [examples](./guidelines.md#add-examples) with helpful descriptions
+- Add [links](./guidelines.md#add-links) to related operations and documentation
 
 ## Quality assurance
 
-- ☑️ Preview your changes locally before submitting
-- ☑️ [Lint your API docs](guidelines.md#lint-your-api-docs) to identify and fix issues
-- ☑️ Check all links to ensure they work correctly
-- ☑️ Ensure examples are realistic and error-free
-- ☑️ Validate that your OpenAPI document is well-formed
+- Preview your changes locally before submitting (see [Contribute locally: Elasticsearch quickstart](./quickstart.md))
+- [Lint your API docs](guidelines.md#lint-your-api-docs) to identify and fix issues
+- Check all links to ensure they work correctly
+- Ensure examples are realistic and error-free

extend/contribute/api-docs/workflows.md

@@ -1,9 +1,9 @@
 ---
-navigation_title: Find your team's workflow
+navigation_title: API docs by product
 ---
-# Find the workflow for your API docs
+# How each Elastic product manages API docs
 
-Each team has its own process for producing their OpenAPI files in their respective repositories. This page provides a quick reference to help you navigate to the right resources.
+Each product has a specific process for producing OpenAPI files in the respective repositories. This page provides a quick reference to help you navigate to the right resources.
 
 :::{important}
 Some of the content on this page is relevant to Elastic employees only and therefore some links are to private repos.