Replace README.txt with README.md and remove outdated information

Sonal Gyanani → made their first commit to this issue’s fork.

Changes are fine, but shouldn't be credited.

@Anybody: Do you mean that none of the committers who improved the README.md should be credited?

As far as I can tell, all three made valuable contributions:

1. @Nila Hyalij made the initial patch
2. @Dheeraj Jhamtani kindly created a patch in Gitlab, for easier preview
3. @Sonal Gyanani put the cherry on top, by adding configuration

Denying credit automatically, for a clear improvement, only because it is about a README file is not fair, in my opinion.

Please see #3367061-21: Categorize contributions that could be considered 'gaming the credit system' and propose solutions (policy, automation, etc) → for a discussion about this. Or maybe I misunderstood your comment?

Thanks @ressa sorry maybe I was wrong, I though I had read this as example in a presentation what should not be credited ;) Not my decision.

No problem @Anybody, I just wanted to make sure :)

But please do participate in the discussion in the issue I linked to. I think it is very important to get this misunderstanding that README updates should by definition be seen as gaming the credit system sorted out.

As i see it, it is important to discern between spamming the issue queues with useless PHPCS reports or README screenshots (probably to game the credit system) and actual improvements, such as the one in this issue, where reformatting was done, as well as editing of content.

I believe several of the changes here were unnecessary. For example:

-* You will probably want to change the welcome email (Administration
+- You will probably want to change the welcome email (Administration

In my experience, the * is a more common character to use as a bullet and switching to a - is not a useful improvement. It makes the patch look bigger but is not objectively better.

@greggles: The README.md template → is using dashes and not asterisks.

I think we should streamline the mark up in README's by following that template.

Thanks for sharing that documentation! I'm not sure if that was an explicit choice or not, but I support the documented version. Looking at the history of that pgae I can see it was changed from bullet to dash in 2022, but the revision message is not visible to explain why or how much discussion occurred. Regardless, I'll use - for now.

Great! It's like indentation, should it be four spaces, or two? How about tabs? At some point it just makes sense to make a decision, and stick to that -- be it two or four spaces, or dashes or asterisks. In this case based mostly on Gitlab style.

We should also use this issue to remove outdated information inside the README.

- If a user enters an invalid email or password they will see a message:

"Unrecognized username or password. Forgot your password?"

That message is confusing because it mentions username when all other
language on the page mentions entering their email. This can be easily
overridden in your settings.php file with an entry like this:

```
$settings['locale_custom_strings_en'][''] = [
'Unrecognized username or password. Forgot your password?
' => 'Unrecognized e-mail address or
password. Forgot your password?',
];
```

This is outdated. The validation message is already correct without any changes (implemented through "email_registration_user_login_validate()"). Let's remove it.

Just a few tiny additions, everything LGTM! Final changes review by @Anybody.

Well done @Grevil!

Adjusting the README, based on comments by @LRWebks.

Grevil → credited LRWebks → .

Thanks, @LRWebks!

Automatically closed - issue fixed for 2 weeks with no activity.