docs: Reduce alarmism about docs being outdated

[RobbieNeko]

Purpose of change (The Why)

This alarmism harms the credibility of the docs unnecessarily and evidently scares off some people from using them.

Describe the solution (The How)

Reduce it to a caution from a warning, and in general is less alarmist about the docs being outdated while acknowledging that some parts of them likely are.

Describe alternatives you've considered

• Remove it altogether

Testing

I read it with my eyes

Additional context

I know at least one modder was scared off of using them by it.

Checklist

Mandatory

• I wrote the PR title in conventional commit format.
• I ran the code formatter.
• I linked any relevant issues using github keyword syntax like closes #1234 in Summary of the PR so it can be closed automatically.
• I've committed my changes to new branch that isn't main so it won't cause conflict when updating main branch later.

[autofix-ci]

Autofix has formatted code style violation in this PR.

I edit commits locally (e.g: git, github desktop) and want to keep autofix

1. Run git pull. this will merge the automated commit into your local copy of the PR branch.
2. Continue working.

I do not want the automated commit

1. Format your code locally, then commit it.
2. Run git push --force to force push your branch. This will overwrite the automated commit on remote with your local one.
3. Continue working.

If you don't do this, your following commits will be based on the old commit, and cause MERGE CONFLICT.