Fixed bug in Contributor Guidelines page

[divine7022]

@dlebauer
Fixes in Contributor Guidelines Page

Resolved Issues:

• Fixed the "How to apply?" link, which previously redirected to a "Page Not Found" error.
• Updated the Slack link, which was previously not linked.
• Maintained the correct structure of the page for better readability.

Let me know if you want any improvements!
Thank you!

[dlebauer]

is this duplicated by #96?

[divine7022]

is this duplicated by #96?

@dlebauer Thanks a lot for your review sir!
This PR(#95) is not same as #96 . Theis PR address the following bug fixes in the given below image:

Resolved Issues:
Fixed the "How to apply?" link, which previously redirected to a "Page Not Found" error.
Updated the Slack link, which was previously not linked.
Maintained the correct structure of the page for better readability.

[dlebauer]

@divine7022 this PR contains the same changes in src/pages/gsoc.js lines 31, 52, 58 in src/pages/gsoc.js as in #96. Perhaps you didn't intend to commit this file in this PR?

[divine7022]

@divine7022 this PR contains the same changes in src/pages/gsoc.js lines 31, 52, 58 in src/pages/gsoc.js as in #96. Perhaps you didn't intend to commit this file in this PR?

@dlebauer
My apologies, it was unintentional to commit the changes from #96 . It happened by mistake.
Thanks for pointing it out!.

[divine7022]

@dlebauer Hello sir!
Just to clarify, should I delete the file (src/pages/gsoc.js) from PR #96?

[dlebauer]

Just to clarify, should I delete the file (src/pages/gsoc.js) from PR #96?

In this case since it is so small it probably won't matter. Worst case is that we can take care of it if a merge conflict arises.

But bigger picture, it is useful to make sure that you keep commits to a single branch so that the changes don't get duplicated - in some cases it can get tricky and confusing to sort out.