Acronyms involving hyphen or "X" is not recognized properly

[amimas]

There are certain acronyms that is expanded slightly differently. For example:

• CIDR is expanded as "Classless Inter-Domain Routing"
• JMX is expanded as "Java Management Extension"

In these cases, even though the acronyms have been expanded, the rule does not recognize it because the expansion pattern is slightly different. For the first example, there's a hyphen (-) and for the second example, the last letter of the acronym does not start with the same letter when expanded.

[amimas]

Found one more scenario where this rule does not work. For example: it does not work if the acronym expanded contains another acronym.

• 1:1 error "JWT" is unexpanded acronym. What does "JWT" stand for? unexpanded-acronym

In this case, even though I have expanded the acronym JWT as JSON Web Token, the rule still sees this as an error because the unexpansion itself contains an acronym (JSON). If I were to expand it as Json Web Token, then it works.

[amimas]

Also, this rule should work if an acronym had been expanded prior to where it was first introduced. For example, the following I think is valid but the rule detects this as an error because it's expecting the acronym to be expanded after it was mentioned.

• It will be using an external proxy, such as an Amazon Elastic Load Balancer (ELB)