Hi Chris, it might be a terrible idea. However, it's how most companies fix their data errors. When not using ES, I wouldn't know of another way.
I agree that implementing a function that updates the CUSTOMER table for an AddressCorrectedEvent is not that much work but you need to think about it up front and there might be other XXXCorrectedEvents you will need to implement.
I'm not saying it's not doable, it's just more complex than sometimes needed if you would've just gone the CRUD/easy/dirty way.