Hey @Ryan,
If things seem to work fine for now, then you don’t need to do anything.
However, the point of this error message is to highlight that if you set your “Events slug” option to something, you cannot have a page that uses that same slug. It can cause issues.
So, for example, the default “Events slug” is /events. Well, if you have a page called EVENTS like on your site, and this page itself also has the slug /events, then now there are two things on your site trying to use the slug /events. This can cause problems.
Hence that error message.
To fix that you can either delete the EVENTS page, or just change its slug to something else.
OR you can head to Events > Settings in your wp-admin and change the “Events slug” option to something other than /events, like /calendar or /agenda or /classes or whatever fits your site’s needs.
As long as the same slug is being used for both things, there might be issues. Things might also work fine for a while, which seems to be the case on your site right now – so, again, you do not have to change anything. But if you want that error to go away and/or want to ensure proper functionality, then doing one of the solutions I mentioned above is the best step.
I hope this information helps!
Cheers,
George