Wikipedia:Peer review/Graybar Electric Company/archive1
Graybar Electric Company[edit]
- A script has been used to generate a semi-automated review of the article for issues relating to grammar and house style; it can be found on the automated peer review page for November 2008.
This peer review discussion has been closed.
I've listed this article for peer review because because I have recently developed this article considerably, and would like positive and creative feedback on how I can improve it as much as possible, and to possibly move it from Stub Class to GA-Class.
Thanks, Wdfadude (talk) 17:02, 14 November 2008 (UTC)
Ruhrfisch comments: Very briefly, here are some suggestions for improvement.
- The lead should expanded to 2 or 3 paragraphs per WP:LEAD. The lead should be an accessible and inviting overview of the whole article. Nothing important should be in the lead only - since it is a summary, it should all be repeated in the body of the article itself. My rule of thumb is to include every header in the lead in some way
- Biggest problem I see with this article is a lack of references - without them it will not make GA, let alone FA. My rule of thumb is that every quote, every statistic, every extraordinary claim and every paragraph needs a ref. As one example of many, the whole "Early History" section has no refs.
- Per WP:CITE references come AFTER punctuation, and are usually at the end of a sentence or phrase, so fix Graybar's revenues had increased to $4.1 billion[11] in 2004, $4.3 billion in 2005[12], and a then-all-time high of $5 billion in 2006. for example.
- Internet refs need URL, title, author if known, publisher and date accessed. {{cite web}} and other cite templates may be helpful. See WP:CITE and WP:V
- There are several one and two sentence paragraphs that need to be combined with others, or perhaps expanded - as it is they break up the flow of the article.
Hope this helps. If my comments are useful, please consider peer reviewing an article, especially one at Wikipedia:Peer review/backlog (which is how I found this article). Yours,