fix: typos, should always include JSON Schema, not only JSON
#1171
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
Welcome to the JSON Schema Community. Thanks a lot for creating your first pull request!! 🎉🎉 We are so excited you are here! We hope this is only the first of many! For more details check out README.md file.
DhairyaMajmudar
approved these changes
Dec 16, 2024
benjagm
requested changes
Dec 17, 2024
Co-authored-by: Benjamin Granados <[email protected]>
built with Refined Cloudflare Pages Action⚡ Cloudflare Pages Deployment
|
benjagm
approved these changes
Dec 18, 2024
|
Congratulations, @jeremyfiel for your first pull request merge in this repository! 🎉🎉. Thanks for your contribution to JSON Schema! |
valeriahhdez
pushed a commit
to valeriahhdez/website
that referenced
this pull request
Dec 19, 2024
…n-schema-org#1171) * fix: typos, should always include `JSON Schema`, not only `JSON` * Update pages/ambassadors/index.page.tsx Co-authored-by: Benjamin Granados <[email protected]> --------- Co-authored-by: Benjamin Granados <[email protected]>
valeriahhdez
added a commit
that referenced
this pull request
Dec 19, 2024
* add json schema conference blog images * add JSON Schema conference article * fix code quality * Update pages/blog/posts/apidays-paris-2024-recap.md Fix 2023 typo Co-authored-by: Ben Hutton <[email protected]> * Update apidays-paris-2024-recap.md Fix apidays brand name and add figure tags * Update apidays-paris-2024-recap.md Correct all occurrences of the apidays brand name. * fix: typos, should always include `JSON Schema`, not only `JSON` (#1171) * fix: typos, should always include `JSON Schema`, not only `JSON` * Update pages/ambassadors/index.page.tsx Co-authored-by: Benjamin Granados <[email protected]> --------- Co-authored-by: Benjamin Granados <[email protected]> * Fix: Removing type failure and Restructring ambassadors page (#1173) * fix:restructring ambassadors page * Ambassador type fix * reverting the changes related to imports * fix: amabassadors import statement fixed * route fix * Update apidays-paris-2024-recap.md Add space between figure one and paragraph; update date --------- Co-authored-by: Ben Hutton <[email protected]> Co-authored-by: Jeremy Fiel <[email protected]> Co-authored-by: Benjamin Granados <[email protected]> Co-authored-by: Dhairya Majmudar <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce?
fix typos for the naming
JSON SchemaIssue Number:
Screenshots/videos:
If relevant, did you update the documentation?
Summary
Does this PR introduce a breaking change?