Multiple instances of this; for example, see here.
And here.
Evidently, more than one storage slot has been used in these contracts and as such the gap var should reflect this.
The incorrect storage gap size could lead to potential issues during future upgrades. If new variables are added in upgraded versions, they might overwrite the storage gap, potentially causing storage collisions and unexpected behavior.
Adjust the storage gap size to account for the storage slot already used in all instances where upgrades could occur.
This ensures that the total number of storage slots reserved for the contract (including both used slots and the gap) remains at 50, maintaining the intended/safe storage layout for future upgrades.
