Thanks so much for the detailed review! I've implemented all your suggestions. I did want to respond to a couple of points, below:
I think it would be good to add a very short section (one or two sentences) after the "Incorrect edits are..." section.
== Overall editing guidelines ==
Some editors have not had an opportunity to read through the editing procedures discussed in the Waze Map Editor
documentation. In many cases, that documentation helps new editors much more than they realize. Be sure to check it out.
Each section should link back to the WME manual or applicable style guide page that gives the detailed guidance for that issue. The basic information would be on this page and the details would be left to the manual or style guide. That would:
- enable this page to be shorter and not look so intimidating
- prevent maintenance of data in two different places if (when) it changes
There's now a "Further reading" section at the end of the article, with links to all five of the introductory wiki articles on editing of which I'm aware. Also some links to the forum. I adapted this from the page for Area Managers.
I'll confess to some concern that, from a beginner's perspective, the Waze wiki may seem encyclopedic rather than tutorial in both treatment and organization. For example, if I go to the Road types (USA) Ramp article
, I see many things that I still do not understand, such as a J-turn (which the article helpfully explains is an RCUT/"Superstreet"). Of course I can find out what this is quickly, but the point is that parts of our documentation aren't especially tutorial in nature.
(It's an interesting aside that Wikipedia is of course intended as an online encyclopedia. So perhaps it is natural that any documentation system based on their engine might tend towards an encyclopedic rather than tutorial presentation.)
So, in writing an article explicitly oriented towards beginners making beginner mistakes, I felt that information should be immediately accessible as well as tutorial in scope. In some cases that meant reiterating information available in other articles. This was deliberate.
That being said, I'm in complete agreement that links to other documentation definitely belong throughout this article. I've been adding them as I go, and welcome help! I also plan to keep adding images as I come across good candidates.
Thanks again for the terrific review and suggestions!