From ab3bdaaa4d48979cf25f5d492fc5c6e358b1e0e0 Mon Sep 17 00:00:00 2001 From: karlchillmaid Date: Mon, 16 Sep 2019 15:56:29 +0100 Subject: [PATCH] Change 'was not' to 'could not be' MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Change 'was not' to 'could not be' – makes it sound more like there's a problem with the email address, and not a problem with the service. --- .../views/service-settings/email-reply-to/_verify-updates.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/app/templates/views/service-settings/email-reply-to/_verify-updates.html b/app/templates/views/service-settings/email-reply-to/_verify-updates.html index 515e55fb7..a985fb8da 100644 --- a/app/templates/views/service-settings/email-reply-to/_verify-updates.html +++ b/app/templates/views/service-settings/email-reply-to/_verify-updates.html @@ -29,7 +29,7 @@ There’s a problem with your reply-to address

- We sent an email to ‘{{ reply_to_email_address }}’ but it was not delivered. + We sent an email to ‘{{ reply_to_email_address }}’ but it could not be delivered.

You can try again, or use a different address.