alexlundin

This is the long description. No limit, and you can use Markdown (as well as in the following sections).
For backwards compatibility, if this section is missing, the full length of the short description will be used, and 
Markdown parsed.
A few notes about the sections above:
<ul>
<li>“Contributors” is a comma separated list of wp.org/wp-plugins.org usernames</li>
<li>“Tags” is a comma separated list of tags that apply to the plugin</li>
<li>“Requires at least” is the lowest version that the plugin will work on</li>
<li>“Tested up to” is the highest version that you’ve successfully used to test the plugin. Note that it might work on 
higher versions… this is just the highest one you’ve verified.</li>
<li>
Stable tag should indicate the Subversion “tag” of the latest stable version, or “trunk,” if you use <code>/trunk/</code> for 
stable.
Note that the <code>readme.txt</code> of the stable tag is the one that is considered the defining one for the plugin, so 
if the <code>/trunk/readme.txt</code> file says that the stable tag is <code>4.3</code>, then it is <code>/tags/4.3/readme.txt</code> that’ll be used 
for displaying information about the plugin. In this situation, the only thing considered from the trunk <code>readme.txt</code> 
is the stable tag pointer. Thus, if you develop in trunk, you can update the trunk <code>readme.txt</code> to reflect changes in 
your in-development version, without having that information incorrectly disclosed about the current stable version 
that lacks those changes — as long as the trunk’s <code>readme.txt</code> points to the correct stable tag.
If no stable tag is provided, it is assumed that trunk is stable, but you should specify “trunk” if that’s where 
you put the stable version, in order to eliminate any doubt.
</li>
</ul>
<h3>Arbitrary section</h3>
You may provide arbitrary sections, in the same format as the ones above. This may be of use for extremely complicated 
plugins where more information needs to be conveyed that doesn’t fit into the categories of “description” or 
“installation.” Arbitrary sections will be shown below the built-in sections outlined above.
<h3>A brief Markdown Example</h3>
Ordered list:
<ol>
<li>Some feature</li>
<li>Another feature</li>
<li>Something else about the plugin</li>
</ol>
Unordered list:
<ul>
<li>something</li>
<li>something else</li>
<li>third thing</li>
</ul>
Here’s a link to <a href="https://wordpress.org/" title="Your favorite software" rel="ugc">WordPress</a> and one to <a href="http://daringfireball.net/projects/markdown/syntax" title="Markdown is what the parser uses to process much of the readme file" rel="nofollow ugc">Markdown’s Syntax Documentation</a>. 
Titles are optional, naturally.
Markdown uses email style notation for blockquotes and I’ve been told:
<blockquote>
Asterisks for emphasis. Double it up for strong.
</blockquote>
<pre><code><?php code(); // goes in backticks ?>
</code></pre>

WP Battle by Alex Lundin

Here is a short description of the plugin.  This should be no more than 150 characters.  No markup here.

Samir Shah

This plugin has two modes – basic and Akismet-enhanced.
Basic mode: the plugin will serve a CAPTCHA to all commenters that aren’t logged in and don’t have a previously approved comment. Repeat commenters will never see a CAPTCHA.
Akismet-enhanced mode (recommended): the plugin will serve a CAPTCHA only if Akismet identifies a comment as spam (much less frequently than the basic mode). Just install an activate <a href="https://wordpress.org/extend/plugins/akismet/" rel="ugc">Akismet</a> to enable this mode.
Note that a CAPTCHA will only appear after a comment is submitted. When a commenter is served a CAPTCHA:
<ul>
<li>If they fail, then the comment will be automatically discarded or trashed (and won’t clutter up your spam queue).</li>
<li>If they pass, it will be allowed into the spam queue (or approved, if you so choose). This means that any false positives from Akismet will be easily identified without you having to trawl through all the spam comments manually.</li>
</ul>
Most genuine commenters will be able to comment on your site hassle-free, without ever seeing a CAPTCHA.
The default CAPTCHA is a simple text-based test. There is also the option to use <a href="http://www.google.com/recaptcha" rel="nofollow ugc">reCAPTCHA</a> if you want something more robust (free API key required). You can also style the CAPTCHA page to fit with your own WordPress theme.
If you come across any bugs or have suggestions, please use the plugin support forum or <a href="http://rayofsolaris.net/contact/" rel="nofollow ugc">email me</a>. I can’t fix it if I don’t know it’s broken! Please check the <a href="https://wordpress.org/extend/plugins/wp-conditional-captcha/faq/" rel="ugc">FAQs</a> for common issues.
Thanks to the following people for contributing translations of this plugin: Belorussian – <a href="http://pc.de" rel="nofollow ugc">Marcis G</a>, Brazilian Portuguese – Stefano, Czech – <a href="http://trumplin.com/" rel="nofollow ugc">Ted</a>, Danish – Jesper, Dutch – <a href="http://wpwebshop.com/books/" rel="nofollow ugc">Rene</a>, Estonian – <a href="http://www.itransition.com" rel="nofollow ugc">Itransition</a>, Finnish – Jani, French – <a href="http://android-software.fr" rel="nofollow ugc">Laurent</a>, German – <a href="http://jochenpreusche.com" rel="nofollow ugc">Jochen</a>, Hindi – <a href="http://outshinesolutions.com" rel="nofollow ugc">Outshine Solutions</a>, Hungarian – <a href="http://www.televizio.sk" rel="nofollow ugc">Gyula</a>, Italian – <a href="http://gidibao.net" rel="nofollow ugc">Gianni</a>, Lithuanian – Mantas, Polish – <a href="http://www.spin.siedlce.pl" rel="nofollow ugc">Pawel</a>, Romanian – <a href="http://simplu.mixnet.ro" rel="nofollow ugc">Lotus</a>, Russian – <a href="http://www.everycloudtech.com/" rel="nofollow ugc">Ivanka</a>, Spanish – <a href="http://www.reinventia.net" rel="nofollow ugc">Reinventia</a>, Swedish – <a href="http://www.umu.se" rel="nofollow ugc">Hugo</a>, Turkish – Tony, Ukranian – <a href="http://www.everycloudtech.com/" rel="nofollow ugc">Ivanka</a>. Some of these translations are a bit out of date – updates welcome!

Conditional CAPTCHA

Asks commenters to complete a simple CAPTCHA if they don't have a previously approved comment, or if Akismet thinks their comment is spam.

WP Battle by Alex Lundin vs Conditional CAPTCHA