Strauss delighted with huge win

England wary of complacency, Dhoni rues Zaheer’s injury.


Afp July 26, 2011
Strauss delighted with huge win

LONDON:


England captain Andrew Strauss said his side had come close to producing the perfect bowling performance to take 20 India wickets during a crushing 196-run win in the first Test at Lord’s.


However, Strauss warned the side not to let their standards drop with the second Test of the four-match series starting at Trent Bridge on Friday.

“It was an outstanding bowling performance by the whole attack over the five days,” said Strauss. “You do have to work hard for your wickets here and I think it showed the value of persistent line and length. That’s the only way of taking wickets and I think we did that brilliantly.”

Ashes-holders England will replace India at the top of the International Cricket Council’s (ICC) Test Championship table if they win this series by at least a two-Test margin. But Strauss added, “We are aware it’s the opening salvo in the series. There’s a lot of cricket still to be played, so we can’t get too satisfied with ourselves.”

Dhoni rues Zaheer’s injury

Meanwhile, India captain MS Dhoni was facing the prospect of being without strike bowler Zaheer Khan in the second Test.

“It became quite tough for us after losing him on the first day,” said Dhoni. “We have three days but I’m not 100 per cent sure if we’ll play him. It’s a long series and we don’t want to risk any individual.”

Trott, Anderson up to 2nd

England’s Jonathan Trott and James Anderson have risen to second place in the International Cricket Council Test rankings after their side’s 196-run win. Trott has climbed two places, above Tendulkar and Sri Lanka’s Kumar Sangakkara, to second spot in the batting rankings while Anderson’s seven-wicket haul saw him overtake teammate Graeme Swann in the bowling rankings.



Published in The Express Tribune, July 27th, 2011.

COMMENTS

Replying to X

Comments are moderated and generally will be posted if they are on-topic and not abusive.

For more information, please see our Comments FAQ