Talk:Lambeau Leap/GA1

GA Review

Article (edit | visual edit | history) · Article talk (edit | history) · Watch

Reviewer: GhostRiver (talk · contribs) 16:58, 17 January 2022 (UTC)[reply]

Hello! I'll be taking a look at this article for the January 2022 GAN backlog drive. If you haven't already signed up, please feel free to join in! Although QPQ is not required, if you're feeling generous, I also have a list of GA nominations of my own right here.

Good Article review progress box

Criteria: 1a. prose () 1b. MoS () 2a. ref layout () 2b. cites WP:RS () 2c. no WP:OR () 2d. no WP:CV ()

3a. broadness () 3b. focus () 4. neutral () 5. stable () 6a. free or tagged images () 6b. pics relevant ()

Note: this represents where the article stands relative to the Good Article criteria. Criteria marked are unassessed

Lede

"where a player" → "in which a player"
Spell out "Los Angeles Raiders"
Spell out and link [{National Football League]]
Per MOS:CAPTION, as a full sentence, that caption should end in a period

Background

Just as in the lede, spell out "Los Angeles Raiders"
"4th quarter" → "fourth quarter" per MOS:ORDINAL
Comma after "tossed the ball to Butler"

Safety concerns

"the NFL" → "The National Football League (NFL)"
"stands reenacting" → "stands to reenact"

Legacy

"all Packers' players" → "all Packers players"
Same MOS:CAPTION comment as above

Notable leaps

Link Detroit Lions

References

In [9] and [12], "SI.com" → "Sports Illustrated"
In [16], "BleacherReport.com" → "Bleacher Report"

General comments

Images are properly licensed and relevant
No stability concerns in the revision history
Copyvio score looks great!

Putting on hold to allow nominator to address comments. Feel free to ping me with questions, and let me know when you're finished! — Ghost River 17:11, 17 January 2022 (UTC)[reply]

Thanks GhostRiver, I believe I have addressed all your comments here. « Gonzo fan2007 (talk) @ 23:49, 17 January 2022 (UTC)[reply]

Thank you for making those changes, passing now! — Ghost River 00:09, 18 January 2022 (UTC)[reply]