Misleading "all content" text on user cancellation

Maybe just "... all content belonging to it" for most of these?

In summary, we're changing the following text when a user account is being deleted:

• Disable the account and keep all content. ---> Disable the account and keep the account's content.
• Disable the account and unpublish all content. ---> Disable the account and unpublish the account's content.
• Delete the account and make all content belong to the %anonymous-name user. ---> Delete the account and make the account's content belong to the %anonymous-name user.
• Delete the account and all content. ---> Delete the account and the account's content.

I think it's a reasonable change and gives a bit more context to the text.

Maybe just "... all content belonging to it" for most of these?

".. all content belonging to it" might work too, but it would be nice if we could use her/him to give some respect as it kind of sounds weird in some cases.

• Disable the account and keep the content belonging to it.
• Disable the account and unpublish the content belonging to it.
• Delete the account and make the %anonymous-name user own all content belonging to it. <----------- Weird
• Delete the account and all content belonging to it.

Crosspost. We shouldn't repeat the word "account" - @ksenzee agrees.

Usability team to the rescue?

I don't think repeating the word account is a problem - it makes it crystal clear. However could replace 'the account' with 'it's'

* Disable the account and keep all content. ---> Disable the account and it's content.
* Disable the account and unpublish all content. ---> Disable the account and unpublish it's content.
* Delete the account and make all content belong to the %anonymous-name user. ---> Delete the account and make it's content belong to the %anonymous-name user.
* Delete the account and all content. ---> Delete the account and it's content.

Adding the "string freeze" tag.

#5 looks good, but obviously should be 'its' and not 'it's' ;)

Yeah, let's just squeeze an "its" into all options. Sufficiently resolves this issue.

Here's a patch with 'its'. Like Monty Python ;)

Patch looks good - looks like a no-brainer to me.

I think we can maybe still squeeze this in as a bugfix. If not, marking it RTBC is the way for someone to tell us that :)

I think this is sufficiently unclear that we can classify as a bugfix.

Committed to HEAD. Thanks!