Polish docs

[izeye]

What kind of change does this PR introduce?

This PR adds a missing ending colon in the basics.md.

Issue Number:
N/A

Screenshots/videos:

N/A

If relevant, did you update the documentation?

N/A

Summary

N/A

Does this PR introduce a breaking change?

N/A

Checklist

Please ensure the following tasks are completed before submitting this pull request.

• Read, understood, and followed the contributing guidelines.

[jagpreetrahi]

Hey @izeye , cau you please provide more detail about this PR , not able to understand what you're trying to resolve.

[izeye]

@jagpreetrahi It's just a missing punctuation mark between the sentence and the next code block like the following in the same Markdown file:

website/pages/understanding-json-schema/basics.md

Lines 50 to 55 in b0c67bd

	This accepts anything, as long as it's valid JSON:
	```json
	// props { "isSchema": true }
	true
	```

[jagpreetrahi]

Can you please mention the issue number also

[izeye]

@jagpreetrahi I didn't create an issue for it. I'm not sure if it's worth it as it's just a small and obvious fix.

[jagpreetrahi]

@izeye , as we begin contributing, it's natural to feel excited to merge PRs. However, the standard practice is to first create an issue (if one doesn't already exist), wait for it to be accepted, and then open a PR. This approach helps maintain clarity and coordination within the project.
If you're new here, I recommend reading the contribution guidelines and the code of conduct first. It's important to follow the proper process when making a PR. Even if the issue seems small, it's still best to create an issue first.
I hope you understand and will follow the standard contribution flow moving forward.

Thanks

[izeye]

@jagpreetrahi I just created this PR through the "Edit this page on Github" link on the website, so I hoped it's okay as-is.

Thanks for the feedback, but I'll wait for maintainers' feedback as I don't want to make any more noise here due to this small fix.