Fix typo: seperate -> separate

[srishti061]

Summary

Fixed a typo in multiple files.

Problem

The word "seperate" was misspelled across 7 files.

Changes

• Replaced "seperate" with "separate" in all affected files

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 09c7e6e9-382b-4dc9-8378-7048d2454bd8

📥 Commits

Reviewing files that changed from the base of the PR and between d54fce8 and 83c5d1d.

📒 Files selected for processing (2)

• en/mkdocs.yml
• en/redirects.yml

✅ Files skipped from review due to trivial changes (1)

• en/mkdocs.yml

---

📝 Walkthrough

Summary

This pull request updates documentation by correcting the misspelling “seperate”/“seperated” to “separate”/“separated” and making a few related formatting and documentation improvements in the affected API reference files and navigation configuration.

Changes

governance-v1.yaml

• Corrected “seperated” to “separated” in the scope parameter wording in the example cURL token request
• Normalized $ref formatting to use double quotes consistently
• Added default: 0 to the offset query parameter schema
• Minor YAML spacing/layout adjustments

service-catalog-v1.yaml

• Corrected “seperated” to “separated” in the scope parameter wording in the authentication cURL example
• Updated the key parameter documentation in GET /services from “Comma seperated” to “Comma separated”

en/mkdocs.yml

• Updated the API Gateway → Advanced Topics navigation entry to reference the corrected page slug: api-gateway/maintain-separate-gateways-per-tenants.md

Walkthrough

This PR standardizes OpenAPI YAML reference formatting in the governance-v1 API reference, adds a default value for the offset pagination parameter, and corrects minor wording and spacing in API documentation text. It also updates the service-catalog-v1 reference text for spelling, and fixes a MkDocs navigation target path.

Suggested reviewers

• chamilaadhi
• tharikaGitHub

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description only includes Summary, Problem, and Changes; it is missing most required template sections.	Add the missing template sections, especially Purpose, Goals, Approach, Release note, Documentation, tests, and security details.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title is concise and accurately describes the main change: a typo fix from 'seperate' to 'separate'.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In
`@en/docs/reference/product-apis/governance-apis/governance-v1/governance-v1.yaml`:
- Line 74: Replace the misspelled placeholder "admin_passowrd" with
"admin_password" in the curl auth examples; specifically update the curl lines
that contain the grant_type=password payload (the string
"grant_type=password&username=<admin_username>&password=<admin_passowrd&scope=...")
in both the governance-v1 and service-catalog-v1 YAML docs so the placeholder is
consistently spelled "admin_password".

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 9110c286-778f-4e05-b6f9-e9fdc95dda63

📥 Commits

Reviewing files that changed from the base of the PR and between 5642000 and d54fce8.

📒 Files selected for processing (7)

• en/docs/reference/product-apis/admin-apis/admin-v4/admin-v4.yaml
• en/docs/reference/product-apis/governance-apis/governance-v1/governance-v1.yaml
• en/docs/reference/product-apis/publisher-apis/publisher-v4/publisher-v4.yaml
• en/docs/reference/product-apis/service-catalog-apis/service-catalog-v1/service-catalog-v1.yaml
• en/mkdocs.yml
• en/redirects.yml
• en/tools/config-catalog-generator/data/configs.json

[coderabbitai]

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Standardize the password placeholder spelling across both auth examples.

The same typo (admin_passowrd) appears in both en/docs/reference/product-apis/governance-apis/governance-v1/governance-v1.yaml and en/docs/reference/product-apis/service-catalog-apis/service-catalog-v1/service-catalog-v1.yaml. Updating both to admin_password keeps the docs consistent and avoids confusion in copy/edit workflows.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In
`@en/docs/reference/product-apis/governance-apis/governance-v1/governance-v1.yaml`
at line 74, Replace the misspelled placeholder "admin_passowrd" with
"admin_password" in the curl auth examples; specifically update the curl lines
that contain the grant_type=password payload (the string
"grant_type=password&username=<admin_username>&password=<admin_passowrd&scope=...")
in both the governance-v1 and service-catalog-v1 YAML docs so the placeholder is
consistently spelled "admin_password".