Hi @embrasurespace,
Thank you for bringing this to our attention. From what I can see, the issue seems to be related to the way SureForms adds body classes in the admin, combined with how WPCode adds admin body classes (leading vs. trailing spaces). Due to this mismatch, the page you mentioned ends up having a class name that is not correct.
We’ll adjust this on our end in the next release to prevent this issue, but ideally, SureForms also adjust the way classes are added on their end to prevent such conflicts in the future.