91:
it. Hie thee to the library and borrow a few books, even! Reviewers can't really help with this step, because they are probably less familiar with the subject than you are. Mentioning at the review that you are doing some library-research will probably help spark interest in the review and lead to
60:
page, not the comment on the talk page - the article will be looked over by others at the GA/R page, and sometimes, other issues with an article will crop up there. Most reviewers will be very happy that you've asked - hopefully this means that you're interested in improving the article so that it
64:
Step 4. Ask for help - relevant wikiprojects may be able to help with referencing, and reviewers may, if politely asked, fix up some formatting issues. Referring wikiprojects here may help them understand the process.
30:
can be nerve-wracking for some editors, it can be effectively used as a tool for improvement of the article. Many Good
Articles that have had a review and been kept have later gone on to Featured Article.
109:
is reached quickly, and it's not in favour of keeping the article, just take a deep breath. It's not the end of the world. Better luck next time. You may wish to put points from the review into a
80:. If you're not sure where to put them, look for specific phrases (quotes, numbers) and controversial phrases. Each section should have at least one reference in them, and preferably more.
61:
doesn't have to be de-listed. Asking for clarification is like saying to the reviewer, yes, you may just have a point here, and I'm interested in doing something to fix it.
35:
99:. Once you've added in many citations, including any references for statements mentioned at the review, say so, and ask reviewers to look again at the article.
53:
to understand the criteria against which an article is measured. You may also wish to look at other, similar, GA-class articles to see how they do things.
126:- although this refers to deletion discussion, some of the points on how to constructively comment could be useful to keep in mind for GA/R.
50:
68:
Step 5. the most common reason an article is brought to review is due to referencing problems. This essentially means
56:
Step 3. Ask (politely) for clarification if you don't understand any comments in the review. Ask at the
114:
106:
39:
46:
96:
73:
69:
57:
27:
123:
77:
88:
17:
110:
84:
42:
can only help make the review process more pleasant for everyone.
95:Step 7. Add your research into the article, using
8:
7:
24:
83:Step 6. Research the topic.
1:
102:Step 8. Rinse and repeat.
140:
117:for future reference.
51:Reviewing good articles
34:Step 1. Don't Panic.
28:Good Article review
97:inline references
92:more comments.
131:
78:reliable sources
139:
138:
134:
133:
132:
130:
129:
128:
22:
21:
20:
12:
11:
5:
137:
135:
89:Google Scholar
74:full citations
45:Step 2. Read
23:
18:User:Malkinann
15:
14:
13:
10:
9:
6:
4:
3:
2:
136:
127:
125:
121:
118:
116:
112:
108:
103:
100:
98:
93:
90:
86:
81:
79:
75:
71:
66:
62:
59:
54:
52:
48:
43:
41:
37:
32:
29:
19:
122:
119:
104:
101:
94:
82:
67:
63:
55:
44:
36:Staying cool
33:
25:
40:being civil
120:See also:
111:To do list
115:talk page
107:consensus
26:Although
47:WP:WIAGA
113:on the
58:WP:GA/R
124:WP:ATA
85:Google
70:inline
87:it.
76:from
16:<
49:and
38:and
105:If
72:,
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.