muba: good stuff.
You may wish to consider the following (mostly minor and occasionally open to debate) re the idiom or syntax:

In Introduction, "Note: this is not a regex tutorial or regex howto." (emphasis supplied) s/or /nor/

likewise, s/If you may ever find /If you ever find / (may)

Jargon: "Before I finnaly start off, let's set some terminology." -- for spelling change to "finally"; for idiom: just omit it entirely.

Rules of Thumb 2: I'm intruding into content here, but I'm troubled by the statement, "when input from external sources may be unsafe." My view: input from external sources is ALWAYS unsafe... even if it's coming from me. No malice is required: "Fat fingeritis" can wreak havoc!

RoT 2: "...etc) is considered 'tainted'." s/is/are/ for subject-verb agreement in quantity;
typo: "Also, thinks like" s/thinks/things/.

also in RoT 2, for brevity: "There are several ways to untaint data, which I am not about to mention here. You should check the above mentioned Perl Security (perlsec) manpage." could be written, "There are several ways to untaint data for which you should check the above-mentioned...."

RoT3: "They are ignorant or else they are malicious." would be less globally applicable to (all) users) if you said, "Some are ignorant; some are malicious." (As written, the current phrase indicts ALL users.)
"...number from 1 to 5, including, you..." s/including/inclusive/
"On the other hand," means (in this useage) that what follows is intended as a counter-example, whereas what actually follows is a supporting or additional example. Suggest one way to improve it would be to drop the quoted phrase, or (and the grammar stiffs will be object to this, replace "OTOH" with "Or"
typo: s/easiliy/easily/

RoT 5. "syntaxis" -- I think you want "syntax" and
"analysis" instead of "analyzing."

RoT 6. spelling: s/shuld/should/

RoT 7. "Do use CGI; (have..." might be clearing if you were to say "Do use CGI:; (have..." or, even better, if you specified the module by its full name
and: "CGI offers you a great amount of functions" can be better phrased "CGI offers you many functions"
and in " good as the module's author." s/good/well/ (good is an adjective, well is the adverb form).

If you find these useful (msg me), I'll carry on with the rest of the document.

Again, ++

In reply to Re: [Try-out] Regexp do's and don'ts by ww
in thread Regexp do's and don'ts by muba

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.