![](https://ftw.usatoday.com/wp-content/uploads/sites/90/2023/03/scheft.jpeg?w=1000&h=600&crop=1)
Monday night’s Cleveland Browns-Pittsburgh Steelers game came with an absolutely crushing injury as running back Nick Chubb was carted off after what looked like a nasty hit to one of his knees.
The moment underscores just how devastating it is when anyone goes down with an injury in football, much less one of the most electric and well-loved players in the NFL.
Well, ESPN NFL insider Adam Schefter found the worst possible way to tweet about Chubb’s injury by leading with the multiple injuries he sustained to one of his knees in college to make it sound like that’s what he got diagnosed with right after being carted off in Pittsburgh.
Nick Chubb dislocated his left knee and tore his MCL, PCL, and LCL with cartilage damage on October 10, 2015 vs. Tennessee. He injured the same knee tonight vs. Pittsburgh.
— Adam Schefter (@AdamSchefter) September 19, 2023
Like, okay Adam Schefter, what on Earth?
In what’s either a befuddling Twitter oversight or a shameless play for eyeballs, Schefter’s poorly worded social media post about Chubb’s injury caught plenty of ire from NFL fans who felt this was the exact wrong message for the moment.
Yeah, nobody was on board for this post from Schefter.
— Danny Heifetz (@Danny_Heifetz) September 19, 2023
What a poor way of phrasing this.
Should be “Nick Chubb injured his left knee tonight.
In 2015, he dislocated the same knee and tore his MCL, PCL, and LCL with cartilage damage vs. Tennessee.” https://t.co/n8nA7ZWuvD
— Jake Brend (@JakeBrendTV) September 19, 2023
Phrasing is very important https://t.co/2awtw4dEeX
— Evan Dammarell (@AmNotEvan) September 19, 2023
Gotta rephrase this and start with the date man. https://t.co/Cv6Y4c9F2I
— Tomer Azarly (@TomerAzarly) September 19, 2023
Reword this colossally misleading and confusing tweet please https://t.co/ZnfJtTnud3
— David Steele (@David_C_Steele) September 19, 2023
this is not the best way to word this, man https://t.co/8mueofsvvT
— Justin Carter (@juscarts) September 19, 2023
There were much less scary ways to send this tweet https://t.co/8PddF50YKt
— Blaiden Kirk (@blaiden) September 19, 2023
dude just start the tweet with “In 2015,” https://t.co/ob4fch4dGZ
— Joshua Brisco (@jbbrisco) September 19, 2023
This tweet on my lock screen stopped me in my tracks. Frame it better. Have some respect for the player. https://t.co/Ge7dFCfZXX
— Sean Jordan (@BaySean) September 19, 2023
Why would you phrase this tweet like this https://t.co/mNi8jAha6u
— dylan sanders (@DillySanders) September 19, 2023
adam schefter knows what he’s doing with this tweet’s wording. don’t let him fool you. https://t.co/n7iqLN3Z48
— Kevin Fielder 🇺🇸🇫🇮 (@TheKevinFielder) September 19, 2023
My man you cannot start the tweet like this https://t.co/fd283ybnXr
— Michael Katz (@MichaelLKatz) September 19, 2023
https://t.co/LXDDdsVd8D pic.twitter.com/tbPwVm9Xze
— Scott Tobias (@scott_tobias) September 19, 2023
https://t.co/MJxAuJ2yQD pic.twitter.com/IFh7PAfs4I
— charles (“you look good” – andy reid) mcdonald (@FourVerts) September 19, 2023
Ay bruh plz start the tweet with the date next time https://t.co/TGrMENp1HW pic.twitter.com/spK0lr9nMR
— Ahmed/The Ears/IG: BigBizTheGod 🇸🇴 (@big_business_) September 19, 2023
Absolutely outrageous way to start this tweet https://t.co/lw9Uk2HcnC
— B.W. Carlin (@BaileyCarlin) September 19, 2023