Skip to content

docs: add glossary.md with common API terms#554

Closed
prakharrrrrrsingh wants to merge 1 commit intokeploy:mainfrom
prakharrrrrrsingh:prakhar-singh-glossary-docs
Closed

docs: add glossary.md with common API terms#554
prakharrrrrrsingh wants to merge 1 commit intokeploy:mainfrom
prakharrrrrrsingh:prakhar-singh-glossary-docs

Conversation

@prakharrrrrrsingh
Copy link

📄 Description

Added a glossary.md file in docs/concepts/ folder that contains common API-related terms like API, Endpoint, REST, etc.

This PR aims to help beginners understand key concepts while exploring the Keploy Docs.


🔗 Related PRs


✅ Checklist

  • Added glossary.md with useful terms
  • DCO signed ✅
  • Structured in the correct folder
  • Follows contribution guidelines

🙋 Request for Review

Hi team! Kindly review and merge. Excited to contribute to Keploy Docs 🚀
cc: @amaanbhati @gouravkrosx

Signed-off-by: Prakhar Singh <22052485@kiit.ac.in>
Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you and congratulations 🎉 for opening your very first pull request in keploy

@amaan-bhati
Copy link
Member

Hey @prakharrrrrrsingh Thanks for raising this pr.
Unfortunately, his PR doesn’t include any meaningful changes, typos and breaking links are supposed or just content changes are to be reported not fixed. You can do so on the specific two repositories that we provided. In the future, please ensure that a PR in this repo is raised only if you’ve made substantial updates or solved a particular issue. This helps keep the process efficient and organized.
This being a part of an assignment in api fellowship would be counted since you were suppsoed to create a pr but wont be merged since this is not that relevant of a change. I’m sure you understand, and I appreciate your cooperation on this. We will be closing this PR for now.

@prakharrrrrrsingh
Copy link
Author

prakharrrrrrsingh commented Jun 18, 2025 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants