change from oas to tyk oas

[yurisasuke]

User description

Description

Related Issue

Motivation and Context

How This Has Been Tested

Screenshots (if appropriate)

Types of changes

• [ ] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)
• [ ] Refactoring or add test (improvements in base code or adds test coverage to functionality)

Checklist

• [ ] I ensured that the documentation is up to date
• [ ] I explained why this PR updates go.mod in detail with reasoning why it's required
• [ ] I would like a code coverage CI quality gate exception and have explained why

---

PR Type

documentation

---

Description

• Updated the API documentation to replace references to "OAS APIs" with "Tyk OAS APIs" for clarity and consistency.
• Added a note indicating that certain features apply only to the Tyk Gateway Community Edition.
• Improved the consistency and clarity of descriptions and summaries across various API operations.
• Standardized parameter descriptions and corrected minor formatting issues.

---

Changes walkthrough 📝

	Relevant files
Documentation	swagger.yml Update API Documentation for Tyk OAS APIs                                tyk-api-documentation/swagger.yml Updated API tags from "OAS APIs" to "Tyk OAS APIs". Added a note specifying applicability to Tyk Gateway Community Edition. Corrected and standardized descriptions and summaries for API operations. Improved consistency in parameter descriptions and formatting. +62/-56

---

💡 PR-Agent usage: Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

[github-actions[bot]]

PR Reviewer Guide 🔍

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ No key issues to review

[github-actions[bot]]

PR Code Suggestions ✨

No code suggestions found for the PR.