Torrey Smith: Healthy or Not, Texans Quarterback Derby

facebooktwitterreddit

Dec 14, 2014; Baltimore, MD, USA; Baltimore Ravens wide receiver Torrey Smith (82) makes a catch prior to the game against the Jacksonville Jaguars at M&T Bank Stadium. Mandatory Credit: Tommy Gilligan-USA TODAY Sports

Welcome to the Daily Caw, where we round up all the latest Ravens news and notes from around the web for your convenience. Today we debate whether Torrey Smith is healthy or not, if the Jaguars discovered the formula to slow down the Ravens offense, the Texans are scrambling to find a healthy quarterback for Sunday’s game, and Jeromy Miles is playing well at the safety position.

Torrey Smith: Healthy or Not?

Jamison Hensley thinks that Torrey Smith looked “healthy” against the Jaguars, and that he simply needed to get back in the rhythm of the game.  I’m not so sure.  If he was truly healthy, why did Smith only see three targets in a game where the offense struggled?  Especially when Steve Smith couldn’t get open?  Sure, Smith didn’t look as hobbled as he did last week, but he isn’t 100%.

More from Ebony Bird

Jeromy Miles Playing Well at Safety

Jeromy Miles has quietly been playing good football lately, even recording his first NFL interception against the Jaguars that sealed the game.  His progress through three games is very encouraging at a position ravaged by injuries and poor play.

What Texans Quarterback Will Ravens Face Sunday?

The Texans have been ravaged with injuries at the quarterback position, much like the Ravens have in the secondary.  After losing Ryan Mallet for the season, they proceeded to lose both Ryan Fitzpatrick and Tom Savage last week.  Now it looks like either Thad Lewis or Case Keenum will start, neither of which is an ideal option for the Texans.

Jaguars Discover Formula For Slowing Ravens Offense?

I’m not so sure they did.  The offense just looked stuck in the mud out there, it wasn’t like the Jags even recorded a single sack. They did “stop the run,” but that just as easily could be attributed to Justin Forsett not being 100% in this game.