@taxidr23 wrote:
Happy to see this specifically addressed as the other replies seemed to dance around the issue.
Definitely. There was an issue with a completely different safe harbor statement, also requiring a signature, that was resolved, Hopefully, the issue with this statement will be resolved as well.
