fix readme.txt issues for i18n

[masteradhoc]

Fixes WordPress/wordpress.org#601
and https://wordpress.org/support/topic/l10n-issue-at-least-for-german/

What?

Fix markdown formatting in readme.txt so that all user-facing strings are correctly picked up by GlotPress for translation on WordPress.org.

Why?

Several sections in readme.txt used standard Markdown headings (##, ###) and a misformatted top-level section (== Redirect After the Two-Factor Challenge ==) instead of the WordPress.org readme format. GlotPress only extracts translatable strings from content inside recognized WP.org sections. Any content nested under ##/### headings was silently ignored by the translation system, leaving a significant portion of the == Description == section untranslated across all locales.

Additionally, two bare URLs in the FAQ section were not wrapped in Markdown link syntax, and one had a stray line break causing a sentence to begin with . It.

How?

• Replaced all ## headings with = Heading = (WP.org subsection format)
• Replaced all ### subheadings with **Bold text** to preserve visual hierarchy without introducing ambiguous heading levels
• Changed == Redirect After the Two-Factor Challenge == to = Redirect After the Two-Factor Challenge = so it is treated as a subsection of == Description == rather than a standalone top-level section
• Wrapped bare URLs in the FAQ in Markdown link syntax and added missing punctuation
• Fixed a stray line break that caused a sentence to start with . It on its own line

Testing Instructions

1. Run the updated readme.txt through the WordPress.org Readme Validator and verify no errors are reported and the preview renders all sections correctly.
2. After deploying to WordPress.org SVN, check translate.wordpress.org/projects/wp-plugins/two-factor and confirm that the previously missing strings (e.g. "Each user must individually configure their two-factor authentication settings", "All methods work on both HTTP and HTTPS sites", the Actions & Filters list entries) now appear as translatable strings.

Screenshots or screencast

Changelog Entry

Fixed - Correct readme.txt formatting so all user-facing strings are extracted for translation on WordPress.org.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: masteradhoc <masteradhoc@git.wordpress.org>
Co-authored-by: jeffpaul <jeffpaul@git.wordpress.org>
Co-authored-by: dd32 <dd32@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[dd32]

Sorry, I stole the linked issue from this repo, without seeing the linked PR.. I considered these to be faults of the plugin directory translation handlers, than the readme format 🙃

[masteradhoc]

Thanks @dd32 even better if you can close this globally so we dont have to do the workarounds :)!