UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.81 Safari/537.36

Steps to reproduce the problem:
1. Open some page (eg. www.getpaint.net)
2. Switch to a different tab so the page loads in the background
3. Switch back to the tab when it's finished loading and check the dev tools for the warning message

What is the expected behavior?

What went wrong?
The warning message isn't grammatically correct:

"Active resource loading counts reached to a per-frame limit while the tab is in background. Network requests will be delayed until a previous loading finishes, or the tab is foregrounded."

In my opinion it should read:

"Active resource loading counts reached a per-frame limit while the tab was in the background. Network requests will be delayed until a previous loading finishes, or the tab is brought to the foreground."

Did this work before? No 

Chrome version: 69.0.3497.81  Channel: stable
OS Version: 10.0
Flash Version: 

Yes, I realise this is extremely nit-picky, but should also be extremely easy to fix and if no one reports it it won't be fixed. So... yeah, I'm spending 5 minutes to report this :)

Here's what I changed and why I changed it:
- Removed the unnecessary "to"
--- It was just plain wrong and didn't make sense.
- Changed "is" to "was"
--- It makes more sense to say "was" than "is" because the limit was reached while the tab was in the background, regardless of whether the tab is still in the background when the message is read. Also, you can only read those messages when the tab is in the foreground (unless you have the devtools undocked) and "is" would make no sense in that case.
- Added a "the" for consistency with the other "the"
--- It was awkward to read.
- Changed "foregrounded" to "brought to the foreground"
--- It makes more sense to use a regular phrase than to invent a new word randomly.