Update README.md

typo

Author: SMcCandlish

README.md

@@ -240,7 +240,7 @@ If you were already using an old version prior to RH Topic Tags v3.0.2, then the
 - Made tags case-insensitive by default; this will stop the common problem of a tag like "chicken" existing and someone typing in "Chicken" or "CHICKEN" instead, requiring manual admin intervention to merge them. They are now auto-merged. There was already some code in RH's original extension that made it clear that case sensitivity was intended to be an administrative choice. This has been extended throughout the codebase, though there is not yet an administrative selector to turn on case-sensitive tagging. That would only be of practical use on a system in which only admins/mods and selected other users were permitted to tag, and only from a predefined list of tags, otherwise the problem of unintentional duplicates would again run rampant.
 - Added SQL injection attack checks to the processing of tag names. While phpBB likely has some of that built into all form processing by default, mine is almost certainly more robust, as it is based on extensive and recently updated research into the types and techniques of this sort of security breach.
 - Streamlined a great deal of the code to be more efficient and less redundant, better documented in comments, clearer to read (e.g. using proper if-else statements instead of ternary notation in most circumstances, since the latter are poorly understood by non-experts), and written in better English.
-- Normalized code in different functions to behave consistently and to reuse existing functionality more. The original extension was clearly developed in "spurts" of activity, without much regard to prior work. E.g. the tagcloud script was producing unnecessary direct calls to the database instead of reusing db-access utility code already written in a script for that work, and was bypassing all access and other security measures in the tagsmanager script.
+- Normalized code in different functions to behave consistently and to reuse existing functionality more. The original extension was clearly developed in "spurts" of activity, without much regard to prior work. E.g. the tagcloud_manager script was producing unnecessary direct calls to the database instead of reusing db-access utility code already written in a script for that work, and was bypassing all access and other security measures in the tags_manager script.
 - Added finer-grained tag size display in the tag cloud.
 - The tag cloud was originally sorting as well as size-adjusting tags based on frequency of use, which basically robbed us of the ability to use the sorting order more sensibly; if tag size already indicates use level, then having tag order do the same thing is redundant and unhelpful. So the order has now been changed to human-friendly alphanumeric, consistent with the rest of the tag displays (in topics and in the ACP's default view).
 - Fixed misspelling of lead dev's name as "Robet" at every place that occurred.