Addresses #6165 by removing incorrect and conflicting instruction

[erictheise]

Removes incorrect and conflicting instruction about not using scheme on "next two variables". Second example does indeed include scheme and first example produces an incorrect link without scheme included.

What type of PR is this? (check all applicable)

• 🍕 Feature
• 🐛 Bug Fix
• 📝 Documentation
• 🧑‍💻 Refactor
• ✅ Test
• 🤖 Build or CI
• ❓ Other (please specify)

Related Issue

Example: Fixes #6165

Describe this PR

See above.

Screenshots

Please provide screenshots of the change.

Review Guide

Notes for the reviewer. Probably look at your own variables in production. Barring that, set up a server using these instructions and check the website link in the upper right header; the domain name will appear as a path on the base server domain not as its own domain.

Checklist before requesting a review

• 📖 Read the Tasking Manager Contributing Guide: https://github.com/hotosm/tasking-manager/blob/develop/docs/developers/contributing.md
• 📖 Read the HOT Code of Conduct: https://docs.hotosm.org/code-of-conduct
• 👷‍♀️ Create small PRs. In most cases, this will be possible.
• ✅ Provide tests for your changes.
• 📝 Use descriptive commit messages.
• 📗 Update any related documentation and include any relevant screenshots.
• 🔠 Does this PR introduce or change any environment variables? If so, make sure to specify this change in the description.

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[mahesh-naxa]

thanks for catching this.