Talk:Washington State Route 163

Latest comment: 11 years ago by TCN7JM in topic GA Review
Good articleWashington State Route 163 has been listed as one of the Engineering and technology good articles under the good article criteria. If you can improve it further, please do so. If it no longer meets these criteria, you can reassess it.
Article milestones
DateProcessResult
January 21, 2013Good article nomineeListed

GA Review edit

This review is transcluded from Talk:Washington State Route 163/GA1. The edit link for this section can be used to add comments to the review.

Reviewer: TCN7JM (talk · contribs) 21:49, 21 January 2013 (UTC)Reply

Not doing anything else today. Why not? –TCN7JM 21:49, 21 January 2013 (UTC)Reply

  1. It is reasonably well written.
    a (prose):   b (MoS for lead, layout, word choice, fiction, and lists):  
    There are a couple issues with the prose, and there are a couple major MoS issues that ruin the entire article for me.
  2. It is factually accurate and verifiable.
    a (reference section):   b (citations to reliable sources):   c (OR):  
  3. It is broad in its coverage.
    a (major aspects):   b (focused):  
  4. It follows the neutral point of view policy.
    Fair representation without bias:  
  5. It is stable.
    No edit wars, etc.:  
  6. It is illustrated by images and other media, where possible and appropriate.
    a (images are tagged and non-free content have fair use rationales):   b (appropriate use with suitable captions):  
  7. Overall: Great effort!
    Pass/Fail: 

References

  • Yeah, we're going to start at the end. Refs 23, 24, 26, and 28 are too long. You should just show the basic stuff and hide the rest using hidden text, otherwise it just makes the section way too long.
  • Note that some of Ref 19 is upside down :p (This has no effect on the article.)

Lead

  • The roadway can't really continue onto the ferry. The designation does, but there's no actual roadway.
  • Comma between renumbering and extending in the second paragraph.

Route description

  • First sentence
  1. "the SR 16 in Tacoma freeway" (Consider rewording)
  2. No comma needed
  • I'd doubt the ferry itself is 1.7 miles long. The route might be, though. (Second paragraph, first sentence)
  • If you're going to use the abbreviation for Washington State Ferries in the last sentence of the second paragraph, put it in parentheses next to its first usage.
  • Comma between year and the. (Last paragraph, first sentence)

History

  • "The corridor was previously been used" (First paragraph, second sentence)
  • "creation of the Primary and secondary state highways" If this is used as the name of a highway system, capitalize all major words. If not, lowercase the first one.
  • I would consider splitting the info about the former SR 163 and the current SR 163 into two paragraphs. If each paragraph looks to small after the split, then you can re-merge them.
  • "The route was extended onto the Point Defiance–Tahlequah Ferry across the Dalco Passage in 1994 with the rest of the Washington state ferry system." I don't really see why the last two phrases need to be included. They're pretty confusing and don't seem to be relevant to SR 163.
  • The background information on the Skansonia seems irrelevant to the route. (Second paragraph, second sentence)
  • The last sentence should be split into two. The Chetzekoma beginning to serve the route has nothing to do with the Hiyu returning briefly.

Major intersections

  • This section is fine, but I'd consider breaking out {{clear}} again to correct the header.

This concludes my review. I'm putting it on hold so you can fix the issues.TCN7JM 23:42, 21 January 2013 (UTC)Reply

Taken all the suggestions into account and hopefully met all concerns. SounderBruce 23:48, 21 January 2013 (UTC)Reply
Alright then. I'll pass the article. Good job. –TCN7JM 23:59, 21 January 2013 (UTC)Reply