not sure, actually. Should "Try again" replace the "Approve" button?

Labeled it as High priority, since similar connection errors might happen quite often, and since it will create not a great first impression, I think we should prioritize fixing it.
This should be fixed once D47074-code is merged
it would look like this:

@Automattic/jetpack-design may I bother you with the sanity check for the above styling update?
The above seems a good fix for me. 👍
Maybe: can we be more explicit on what went wrong? Any chance without being overly technical?
These errors coming from WPCOM's /jetpack-blogs/$clientId/authorize response, so indeed we can iterate on them. Although it might not be a simple change. I'd prefer to leave this fix to remain style-related.
I wonder if we have plans on reviewing these error responses as part of our connection focus? (not sure who to ping about the above question, so cc @kbrown9 @leogermani)
Yes, makes sense to just fix the visual first. I was asking as the first screen was showing something different — let's go ahead. :)
Ah! In a second screenshot I was "simulating" connection error by going offline. Normally there should be meaningful error as in issue description
Deployed via r211170-wpcom
I wonder if we have plans on reviewing these error responses as part of our connection focus?
As you can see from the first screenshot, the current error messages aren't very actionable. We do have plans to work on providing better connection error messages.
Most helpful comment
As you can see from the first screenshot, the current error messages aren't very actionable. We do have plans to work on providing better connection error messages.