Within events and registration forms we offer two ways to limit the amount of registrations that are accepted.  The first way is to limit the number of individual registrants.  This means that each visitor counts as a single registrant, regardless of how many registrations they are allowed to buy.  The second way is to restrict the number of registrations that can be purchased, which actually counts the amount of registrations purchased.

As an example, let's say I go to an event or registration form with limited registrations (say 100) and I buy 3 registrations (one for myself, two for friends).  The first example above would only count that transaction as one registration and would reflect that there are 99 registrations left, which would be accurate according to how that restriction works.  The second method I mentioned above, which is actually a variable that is set directly in the registration type, would reflect that there are now 97 registrations left, because I bought three total registrations.

Both methods are technically correct, but because they count registrations differently, you should never use both of them at the same time as it can be confusing to see two different values for remaining registrations on an event or registration site.