[Documentation] Fix outdated URLs and formatting issues in documentation

[Soumya-codr]

📄 Documentation Cleanup: Fix Outdated Links, HTTP URLs & Formatting Issues

📝 Summary

Several documentation files contain outdated GitHub URLs, insecure HTTP links, and small formatting mistakes. Updating these will improve accuracy, security, and overall documentation quality.

---

🔎 Issues Identified

1. Outdated GitHub URLs using master instead of main

Files affected:

• RELEASE_PROCESS.md
• spec/asyncapi.md (multiple binding URLs)

Problem:
GitHub has migrated default branches to main, but many links still point to /master/, causing redirects or potential 404s.

Examples:

• RELEASE_PROCESS.md — Line 26
  https://github.com/asyncapi/parser-js/blob/master/CODEOWNERS
• spec/asyncapi.md — Lines 1125–1143
  URLs like:
  https://github.com/asyncapi/bindings/blob/master/http#server

Proposed Fix: Replace all /master/ URLs with /main/.

---

2. HTTP link should be HTTPS

File: spec/asyncapi.md
Line: 843

• Current: http://spec.commonmark.org/
• Should be: https://spec.commonmark.org/

Reason: HTTPS improves security and ensures modern compatibility.

---

3. Minor formatting & grammar issues

README.md

• Line 19: </br> → <br>

examples/README.md

• Duplicate word: “the the name” → “the name”

---

📌 Why This Matters

• Prevents broken/redirected links
• Improves documentation security (HTTPS)
• Ensures readability and consistency
• Keeps project aligned with GitHub’s current branch standards

---

✔ Proposed Solution

I would like to open a PR that:

• Updates all outdated /master/ URLs to /main/
• Converts the HTTP link to HTTPS
• Fixes minor formatting and grammar errors

Please let me know if @derberg (maintainers) approve. I’m happy to create the PR.

[Harsh-Sahu43]

Hi, I’m Harsh Sahu. I would like to work on this issue as part of my first open-source contribution.
I can update the outdated /master/ URLs, replace HTTP with HTTPS where required, and fix the noted formatting issues.
Please let me know if I can proceed with a PR.

[Gurleen-kansray]

Hi @Soumya-codr,
I would like to work on this issue.

[Harsh-Sahu43]

Thanks for the update.

I’ve already gone through the issue details and I’m ready to work on the fixes (updating /master/ to /main/, switching HTTP to HTTPS, and correcting formatting issues).

I’ll wait for a maintainer to confirm or assign before proceeding with a PR to avoid duplicate work.
Happy to coordinate if needed.

[Nakul03]

Hey @Soumya-codr I manually verified all the links mentioned in this issue:

• spec/asyncapi.md (lines 1125–1143)
• RELEASE_PROCESS.md (line 26)
• https://github.com/asyncapi/parser-js/blob/master/CODEOWNERS

All of them are currently working and point to valid resources.
The repository uses master as the default branch (no main branch), so the links are correct.

The HTTP links redirect automatically to HTTPS, so no update is required there.

Only the naming-related link appears to need a minor correction.

[SanskarRai]

Hi, I’d like to work on this documentation cleanup issue.
I can either submit one combined PR or split it into smaller PRs
if that’s preferred. Please let me know what works best. Thanks!

[rahulcse129]

I’d like to take this up and open a PR.

[dayanandXdarpan]

I have analyzed issue, identified the necessary fixes.

1.Link Updates: master -> main in RELEASE_PROCESS.md and spec/asyncapi.md.
2.Security: http://spec.commonmark.org -> https in spec/asyncapi.md.
3.Formatting: Fix
in README.md and "the the" typo in examples/README.md.

[animeshk923]

Proposed Fix: Replace all /master/ URLs with /main/.

This will break the current URLs present as no main branch exists. Would not recommend doing it.

---

2. HTTP link should be HTTPS

Current modern browsers automatically try to load the https version first. For example:

Chrome will automatically upgrade all http:// navigations to https://, even when you click on a link that explicitly declares http://.
Refer: https://blog.chromium.org/2023/08/towards-https-by-default.html. Para: 3, Line: 1

But as a good practice we should have https.

The example provided (http://spec.commonmark.org/) results to https URL.

---

3. Minor formatting & grammar issues

This we can do with an external tool. Separate issue can be opened after discussion with maintainers.

[Soumya-codr]

Thanks @Nakul03 and @animeshk923 for the heads-up regarding the branch names! I appreciate you pointing out that master is still the default here I'll ensure I do not touch the branch references to avoid breaking any links.

[Soumya-codr]

@Harsh-Sahu43 @Gurleen-kansray @dayanandXdarpan @rahulcse129 @SanskarRai , thanks for your interest in contributing and also sorry for the late reply guys! Since I raised this issue and have the context on the specific fixes needed (now that we've narrowed down the scope), I'll go ahead and wrap this up myself to avoid confusion.

Plan of Action: I will open a PR shortly that strictly focuses on:

• Updating http to https where appropriate (as validated by @animeshk923).
• Fixing the minor formatting/typos in README.md and examples/README.md.

Working on the PR now. 🚀 (If maintainers will approve this issue)

[derberg]

Please do not open AI generated issues, especially if you do not validate the content, if true.