fix: correct path for pr-contributors.html in index.html (fixes #389)

[Saminakalwar]

Fixes #389

📌 Summary

Corrected the wrong file path for pr-contributors.html in index.html.

🔧 Changes Made

• Updated the link in index.html to point to the correct path for pr-contributors.html.

✅ Checklist

• Bug fix
• Verified the link now works correctly
• Screenshots attached (see below)

📷 Screenshot

Before: (broken link – path not working)
page Before Updation Looked like:

Initial Code link:

After: (fixed link – path working correctly)
Page After Updation Looked like:

Update Code :

[vercel]

@Saminakalwar is attempting to deploy a commit to the vaibhavbabele's projects Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

👋 Hi @Saminakalwar, thank you for opening this Pull Request!
🔧 Please ensure the following:

• ✅ Resolve any merge conflicts, if they exist.make sure you have updated your local repo to avoid conflicts. and solve in your local repo. do not solve in github editor.try to solve in your local repo in vs code or any other editor.
• 🧾 Clearly mention the issue number you are solving (e.g., Fixes #issue_number).
• 📎 Please update your PR description if anything is unclear or incorrect.
• 📷 Attach a screenshot or screen recording of your fix.
• 💬 Kindly share the PR link in the Discord server manually for better tracking.
• if follow the guidelines and fit to project then label according to pr otherwise close the pr.

Happy Contributing! 🚀

[github-actions]

⚠️ Merge Conflict Detected!
Hi @Saminakalwar, your pull request currently has a merge conflict with the base branch. Please resolve the conflict so your PR can be merged.
---
## How to Resolve a Merge Conflict (Step-by-Step)
1. Checkout your PR branch:
bash git checkout fix-issue389

  2. **Fetch the latest changes from the main branch:**
     ```bash
     git fetch origin
     git pull origin main
     ```
  
  3. **Git will show conflict markers in files with conflicts. Open those files, and manually edit them to resolve the differences. Conflict sections look like:**
     ```
     <<<<<<< HEAD
     Your changes
     =======
     Changes from base branch
     >>>>>>> main
     ```
  
  4. **After resolving the conflicts, mark them as resolved:**
     ```bash
     git add <file(s)-you-resolved>
     ```
  
  5. **Commit the resolution:**
     ```bash
     git commit -m "Resolve merge conflict"
     ```
  
  6. **Push your updated branch:**
     ```bash
     git push origin fix-issue389
     ```
  
  ---
  
  🔗 [GitHub Docs: Resolving merge conflicts](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/about-merge-conflicts)
  
  If you need any help, please ask your mentors by replying here!
  
  ---
  
  *This is an automated message to help you resolve merge conflicts and get your PR ready for review. Thank you!*