Follow-up from "Fix plan limits for different types of enforcement alert"

The following discussion from !121920 (merged) should be addressed:

• @drew started a discussion:

  This seems like an important nuance, but one that is lost on me. Did Fulfillment and/or Technical Writing have a look at this? What does included in mean, vs of?

• @drew also had a similar wording nitpick further down. The original MR did add some clarifying language, but that's probably worth having an actual Technical Writing look while we're here:

  This description doesn't seem meaningfully different from storage_size limit below. Can we be more descriptive in either/both of these?

Let's take this opportunity to review the fields related to storage and how can we be clearer in the nuances of each limit

Additionally, we might want to investigate if we can deprecate is_temporary_storage_increase_enabled and temporary_storage_increase_ends_on. From memory I remember this started being implemented but we never finished. This should be handled in #385720 (closed)

Another thing is we might want to review the usage of root namespace vs top level group. Technical Writing can help us with that