Here is the updated spec: https://folio.googleplex.com/full-storage-1
Assets: https://drive.google.com/corp/drive/u/0/folders/0B_2Uyb2Rhx2ON1FjMHVVSjhXb3c

Are these strings replacements for the strings previously implemented (based on mocks in https://drive.google.com/corp/drive/u/0/folders/0B29spHBLr1wTYjNnZFk4TmZxN1U), or are they for a new use case? The wording specifically calls out downloads, which could be confusing if we show it when the user isn't trying to download things.  It also doesn't warn them about potential data loss if they don't act on it.

Thanks for checking. This is the most updated wordings I got in the mock:
https://folio.googleplex.com/full-storage-2#

I will check with Hiro to see if this is what we have confirmed, as I'm not sure if there's any changes to this. 

Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Storage manager was shipped. Yay!
Let's close this issue.

Verified on ChromeOS 	8872.15.0, 55.0.2883.17