I still feel like if the question is going to be mentioned, might as well answer it?

Eh. I feel like it's fine to have it there, and that the sentence flows a bit less without it. Don't feel that strongly about it tho, so i'm cool with removing it if other people pitch in.

and runs the risk of implications about guides being a waste of time

Considering our current issue of guide bloat, especially "required" guides - it's an implication many new users already believe. It's a way to calm them down and say "we know, don't worry."

I'd note "and other phenomena" since there are a lot more types of anomalies than items and monsters?

As mentioned to Viv and Tawny - there are a lot of things here that are technically inaccurate, but the inacurracy is relatively minor so we felt it's fine for the sake of being easy to understand. I tried the suggested punctuation and it felt really awkward.

note sci-fi horror/creepypasta?

Technically inaccurate but easier to parse; see the above.

two sentences for ease of reading/parsing?

I get where you're coming from, but breaking the sentence apart comes off kind of awkward.

I feel like the distinction should be made that this applies to writing and headcanon

I think that distinction is already understandable.

Can trim this down to just "If you're new to the Foundation Universe, there are a few terms…"

I kind of agree with what you mean, but this edit made the first sentence way too short and it felt like something was missing. Couldn't really fit anything there to fill the space that wouldn't be fluff, and since "clinical terms may confuse you" is something we do need to address, I think it's fine there.

this feels a little unnecessarily negative?

Yeah I feel ya. Not sure how to replace it though, since any replacements I can think of either don't properly communicate Disc's job, are hard to parse, or are overly convoluted. I'd love suggestions.

instead of "either way", I would use "Just in case you need to" or "Should it be relevant in the future" or the like

I think "either way" works here.

the start of this sentence already makes the point clear, I think you can trim out this part.

I agreed initially, but the sentence just kind of stops with this edit.

will there be links to the forums as well?

Maybe better not throw people to the forums to ask newbie questions on endless repeat lol

I would use "complex" rather than "convoluted"

I think convoluted is fine here.

maybe "click the rectangle"?

Honestly this feels less easy to understand than "button" lol

maybe "to get a better idea of how the community's tastes have progressed…"?

Eh? That's not really what a new user would really care about. Seeing how the site's writing has changed and evolved sounds interesting, meanwhile "this is what we like nowadays" sounds kinda… boring.

I would note "canon collections"

I feel like that would be even more confusing. "Wait, we collect canons? Why are they collected?" A user who'd be confused by the idea of multiple canons would be even more confused by having so many of them we collect canons.

I think you can just go right to the next sentence?

I don't think so, since the "we've given you enough" is in response to the previous "there's so much we can suggest." It's a way of saying "There's so much more we didn't even cover, but this will do for now."

maybe "want to make a wikidot account for the SCP wiki" since we still get a lot of confused newbies wondering why making a wikidot account doesn't automatically give them SCP wiki membership

We cover that later.

I would use "pages" instead of "ones"

The previous sentence already says "articles," so I think it's fine.

comment on the forums

We say comment in the previous sentence already; minor inaccuracy for the sake of readability.

I would just use "basically"

I think it's fine rn.

"without asking them first"?

"I asked but they didn't answer so I did it anyways." Want to make sure that doesn't happen.

I would reorganize the sentence a bit:

I feel like the reorganized sentence's priorities are a bit weird: It outlines a method before explaining what said method is even for.

In case someone is looking for that info on a skim?

The title ends up looking really, really awkward. Also - maybe best not to help people skip the section where our rules are.

should it be noted that the wait time is 1-2 days max?

That's the wait time for now. God knows what it'll be in the future.

I would remove the "and comes with many of its own quirks and glitches" bit

I think it's fine.

Maybe a lead-in? "If you've gotten to this point, thanks for reading, and welcome to the site" or the like?

Honestly, that feels even more disconnected for me.

"and ideally gotten greenlighted"

I think it's fine for now.

maybe note the "formatting" tab?

I don't think that's particularly needed.

maybe append "perfect at predicting the community response" or the like?

I feel like that changes the meaning of the sentence a tad. "Nobody is perfect" means 'as hard as you try, your article will have some flaws, so don't expect a masterpiece.' "Nobody is perfect at predicting the community response" changes it to be more akin to 'even if you have a perfect article, some people will not like it for some reason.' Also, I don't think we should tell people to write for an audience rather than themselves right out the gate.

should there be a direct link to the Contribute page?

I think it's better for them to try using it themselves, since they'll need to know where Contribute is if they wanna post more articles.

should there be some info on what is usually included in an author post?

…Maybe? It feels useful but also like it might be a bit distracting.

remove the "too"?

IMO it's fine.

I'd rephrase to "writing for the SCP wiki is meant to be a hobby and shouldn't…"

Some people take their hobbies way too seriously, so I think it's better to be more clear here.

Should this be addressed?

I broke it up into two bullet points.

• "How do you pronounce Keter?" > I still feel like if the question is going to be mentioned, might as well answer it? Else just trim this out?
• hopefully without wasting too much of your time. > I feel like this can be removed. It doesn't come off as funny, and runs the risk of implications about guides being a waste of time
• best way we can describe the stuff we have here - Anomalies; items and critters > I'd note "and other phenomena" since there are a lot more types of anomalies than items and monsters? Also, the punctuation is a little weird to parse here. Maybe instead a colon, then a comma instead of a hyphen and semicolon?
• The wiki started as a horror/creepypasta site > maybe note sci-fi horror/creepypasta?
• The wiki started as a horror/creepypasta site so the majority of the older content is focused around that, but since then we've expanded our horizons and nowadays you can find any type of writing you'd want from novella-length adventures to one-line jokes. > I would make this two sentences, or add more commas.
• To reach over ten thousand articles onsite, we had to let go of the idea of a singular "canon", meaning that every article on the site is allowed to contradict and disregard any other article, no matter how well known or popular. > ditto above, two sentences for ease of reading/parsing?
• Did someone say the Foundation was formed in the 1960s, but you need the Foundation to exist in WWI? The Foundation is now from the 19th century, sure. You want a Foundation that has more resources than the eye can see? Go wild. > I feel like the distinction should be made that this applies to writing and headcanon, moreso than just "I think this, therefore it is like this".
• - many articles can share the same universe, and some explicitly reference each other - it just means that you don't have to try to fit everything into a singular version of the Foundation. > I would make this a separate sentence
• Due to the scientific and clinical tone most of the site aims for, there are a few terms used in articles that may confuse new readers > I'm not sure the object classes are inherently scientific or clinical? Can trim this down to just "If you're new to the Foundation Universe, there are a few terms…"
• This is not a comprehensive list of such terms, but other unfamiliar words may be listed in our Glossary of Terms > the "but" reads a little oddly. Maybe instead, "terms; other unfamiliar…"
• Writing isn't all we have to offer > I would say "the site has to offer"
• Staff are site members that > I think it's members "who"?
• dealing with awful people in chat > this feels a little unnecessarily negative?
• the two that are most relevant here > maybe some more clarity instead of just "here"? Most relevant for an introduction, most relevant for day-to-day site activities, something else? The intent of the context isn't super clear to me.
• either by not exactly fitting > "either because the case doesn't exactly fit"
• or relating to incredibly sensitive topics > "or because the case relates…"
• Either way, we recommend having a general idea of how to contact AHT. > instead of "either way", I would use "Just in case you need to" or "Should it be relevant in the future" or the like
• rather than general information which might not be as relevant to your interests > the start of this sentence already makes the point clear, I think you can trim out this part.
• If these guides still didn't answer a question you were curious about, and it's not on the Frequently Asked Questions page, feel free to go to our official chat's help-desk and get assistance from our staff members. > will there be links to the forums as well?

• long, convoluted articles > I would use "complex" rather than "convoluted"
• paragraph spacing in the tabs is inconsistent?
• "click on the button" > maybe "click the rectangle"?
• is the oldest work on the site > maybe "contains the oldest works on the site"? There's some more recently written Series 1 stuff.
• or Top Rated Pages By Year to get a better idea of how the site has progressed and changed over time. > maybe "to get a better idea of how the community's tastes have progressed…"?
• we do have a number of canons > I would note "canon collections", since to a new reader unfamiliar with what a canon is, it might read weird to see "we don't have a single canon, we have a number of canons"
• However, we've probably given you enough already. > feels a little downer-ish/negative. I think you can just go right to the next sentence?

• you want to make an account for the SCP Wiki. > maybe "want to make a wikidot account for the SCP wiki" since we still get a lot of confused newbies wondering why making a wikidot account doesn't automatically give them SCP wiki membership
• vote and comment on existing ones > I would use "pages" instead of "ones"
• post to the forums > comment on the forums
• interact with the site in almost every way you'd like > I would say "interact with the site in various other ways"
• without their explicit consent > I would use "permission"
• In a less robotic way > I would just use "basically"
• without them allowing you to do so beforehand > "without asking them first"?
• The Foundation is fictional, and we'd rather not have RP spaces on our site. > maybe instead "and participation in the SCP wiki is meant to be out-of-character."
• While normal site members cannot comment on 05Command proceedings > "While SCP wiki site members cannot comment directly on the 05Command site"
• Additionally, once you've been active for a while and feel like you can help contribute to the site's functioning, there are semi-frequent staff recruitment threads on the site forums which you are more than welcome to sign up for. > I would reorganize the sentence a bit: "Additionally, there are semi-frequent staff recruitment threads on the site forums which you are more than welcome to sign up for, once you've been active for a while and feel like you can help contribute to the site's functioning"
• The Wiki & Wikidot > Maybe note in the title that this has information on making a wikidot account? Maybe "The Wiki & Wikidot, and making an account" or the like? In case someone is looking for that info on a skim?
• If you've properly done the previous steps, in a few days you should be a member of the wiki. > should it be noted that the wait time is 1-2 days max?
• Our platform is not the best, and comes with many of its own quirks and glitches, but we work with what we have. > I would remove the "and comes with many of its own quirks and glitches" bit
• Welcome to the site! > this is kind of floating/feels added as an afterthought. Maybe a lead-in? "If you've gotten to this point, thanks for reading, and welcome to the site" or the like?

• addenda1. > remember that the period should go before the footnote so it displays right (the number hovers over the period rather than there being a space)
• GoI to GoI. The format structure of each GOI > inconsistent capitalization
• Includes site dossiers and collaborative pages. > I would state "collaborative logs", since we have collaboration pages that are tales and SCPs
• After that, you need to join the SCP Sandbox site > users can create sandbox pages whenever they want, not necessarily only after getting greenlit. Sometimes users draft their concept critique post in a sandbox so they don't need to make a lot of edits to a forum post. Maybe, "To have a place to hold and work on your drafts, you need to join…"
• Once you've made a sandbox page and possibly gotten greenlighted, you're good to start writing your article. > "and ideally gotten greenlighted"
• which gives several important pointers and a basic format to follow. > maybe note the "formatting" tab?
• No matter how much of an amazing writer you may be, nobody is perfect > maybe append "perfect at predicting the community response" or the like? Just because an author really likes their work doesn't mean the community will feel the same, and I feel like there should be a nudge to the element of writing for an audience.
• you may post. > post your work to the mainsite?
• For all other pages: Click the "Contribute" button under the "Resources" tab of the top bar > should there be a direct link to the Contribute page?
• create an author post under your page's discussion thread. > should there be some info on what is usually included in an author post?
• Don't feel too pressured to post. > remove the "too"?
• Writing for the Wiki isn't all that important and shouldn't affect your wellbeing. > I'd rephrase to "writing for the SCP wiki is meant to be a hobby and shouldn't…"
• A blank page is usually intimidating > I'd rephrase to "can be intimidating"
• The third bullet point in the "Pointers and General Tips" list doesn't actually start with a direction, and doesn't match the rest of the bullets. Should this be addressed?

The Anti-Harassment team

Capital "T" in "team" for consistency (it's spelled with a capital T in the previous paragraph).

Sign up to the platform1,

Move this comma after the bracket. "ask around),"

Finish reading the guide first, there's some side-notes about signing up further down.

"Finish reading this guide first. There's some side-notes about signing up further down."

since without a greenlight, you can't use the onsite feedback forums.

"since without two greenlights you can't use the Draft Forum." Two greenlights, not one. Users can obviously use the Ideas Forum before getting greenlights, and the Ideas Forum is an onsite feedback forum so…

Most articles which have a lot of effort put in end up doing well, but sometimes a piece of writing may not work out with the community. That's okay and expected, even for the most experienced authors on site.

This is really good.

Goddamnit I wrote a reply here and it all got deleted. If some of the comments feel rushed at the start - it's cause I had to remember what I said before and summarized it.

Oh no. That's fair though, and it looks good.

As I replied to Mooagain - this change wouldn't help us, since anyone who would ask to be staff straight out would not be deterred by this, and anyone who wouldn't would feel talked down to. No demographic wins.

Sometimes users just… don't know that they have to contribute to the community before they can be staff. Sometimes people will ask out of curiosity because they don't know how staff get recruited or whether they're eligible, and this is written as "how do i become staff?" It then becomes a thing of figuring out whether they're asking to be staff while having been on site like two minutes (which also often indicates a user is underage) or whether they're asking how staff works. More visible detail on how staff recruitment works and who can/should apply for it is good, especially since multiple teams with recruitment threads are needing people. I don't think having it written in the guide would deter the people who expect to be staff straight off the bat from asking, but it would direct people who are curious about staff recruitment to the recruitment threads without them having to ask. Some users may not think or want to ask how it works, but if they see it written in a guide that/how they can work towards being staff, they might be more inclined to use the recruitment threads. Ultimately, I'm fine either way on this point, but I do think there should be a line suggesting that users asking to be staff immediately are less likely to be staff but hey here's a bunch of things you can do first if that's something you're aiming to be.

Additionally, a concern of mine is that if we put "Wikidot is a Platform" before "How to Apply", people might just skim it to get to the applying section.

People may skim the entire guide just to get to the applying section. The issue here is that users are told to make a wikidot account before they are told they can't use email addresses with numbers or facebook login to do that. It's fairly common that users come into 17 asking why wikidot isn't sending them the email, and this could be avoided for any user who reads the guide up to the point of the applying section if it was noted earlier in the guide, either by swapping the sections or moving the sentence about numbers in emails into the applying section. Swapping the sections would also push the stuff about the sandbox being a separate wiki, which is also a common query, further up the guide but honestly I'd be fine with just moving the emails in numbers/facebook login sentences into the previous section.

"It's fine if something you work hard on and like ends up being deleted. It's a normal part of the process, and you shouldn't take it as a failure."

This was in fact what I understood you were trying to say in the guide, but it isn't how it comes off.

At this point in the guide, the draft page is empty so they can't ask for crit nor post, which only really leaves drafting.

I mean, the draft page might not be empty. There's nothing stopping a user from writing a draft in the sandbox as long as they have access to the sandbox. Users are permitted to start drafting before they get greenlights, and I think "Once you've made a sandbox page and optionally gotten greenlights, you're good to start writing a draft" is a clear and reasonable sentence.

Possibly change "critters" to something else, because it does mean "reviewers" onsite and I think people may get confused.

The people who'd get confused by this are people who already know what anomalies are, so I don't think their confusion will be all that detrimental. I'm ambivalent to this change and am more than willing to change it if you have a better replacement, but I feel like as it stands it'll be fine.

For Object Classes, MTF, and GoI, maybe include hyperlinks to the main pages for those things so it's easy for new users to navigate to if they're wanting to learn more.

We tried to avoid having too many outgoing links in the Newcomer guide to avoid people feeling like they have to read the links to not "get a lesser experience." Since this is meant as a primer rather than a comprehensive detailing, I think it's fine not to have them.

"general information which might not be relevant to you:"

This edit ended up having two "to you"s in quick succession. I did edit it to fit your general intention with this edit, though, so check it if you can.

"You'll find that everything included in an article or guide (excluding links to separate pages, but including tabviews and collapsibles)…"

I feel this makes the sentence very awkward, because we have "this applies to EVERYTHING (you know, except these things. but not to these things. so actually maybe not everything)." The existing sentence still conveys the same general meaning, so I think it's ok.

This is hilarious. However, as funny as it is and as much as I would like to be able to say it sometimes, I would personally not consider "your article sucks balls" to be acceptable critique…

I agree, which is why the next line clarifies that even if you want to say it, you absolutely should not. Someone who'd miss that will miss anything else we throw at them, and for those who do read I feel like the comedy helps keep this line memorable in their heads.

Perhaps mention something here about how users can ask staff if they aren't sure whether they're violating/close to violating a rule or guideline.

Good advice, but maybe not directly proceeding rule 0, since it could lead to a lot of rule lawyering. "If you don't know something ask someone" is already in the Newcomer Guide, and #site17 mentions are sprinkled throughout the guides.

I'm sure this is just my personal opinion, but I think something should be included here about not asking to be staff straight off the bat.

As I replied to Mooagain - this change wouldn't help us, since anyone who would ask to be staff straight out would not be deterred by this, and anyone who wouldn't would feel talked down to. No demographic wins.

I also think this section should be moved to before the previous one because it mentions that wikidot does not like emails with numbers in them, and also I do not believe very many people will read this section if it's after the previous one.

On the other hand, this section also relies on some stuff mentioned in the previous section, like wikidot being a hosting platform. Additionally, a concern of mine is that if we put "Wikidot is a Platform" before "How to Apply", people might just skim it to get to the applying section. Again - we're trying to aim this mostly towards a reasonable audience rather than people who'll drop the guide the instant they found what they were looking for, since the latter group will neatly ignore anything we try to help them with regardless.

Hmm. Yes, but also it's best not to encourage authors to throw their drafts at the mainsite.

As with the previous section - users who'll selectively read the guide are going to do these fuck ups anyways since they came into the guide with preconceived notions of what they want to gain from the guide. This is written so far back because it's one of the biggest worries people have about posting to our wiki, even people from other branches of SCP. Also, I think you misunderstood what this was meant to say - "It's fine if something you work hard on and like ends up being deleted. It's a normal part of the process, and you shouldn't take it as a failure." This isn't specifically relevant to coldposting.

It's also not a necessity to be greenlit unless a user…

Seems we fixed this while you were writing your comment lol.

This is pretty vague.

I don't think so, personally. At this point in the guide, the draft page is empty so they can't ask for crit nor post, which only really leaves drafting.

Maybe add something about reserving space for author posts.

This is useful, but I think that it's not something uber essential to point out here considering how wordy the explanation ends up being, as opposed to a very minor potential loss.

items and critters

Possibly change "critters" to something else, because it does mean "reviewers" onsite and I think people may get confused.

who's job it is

"whose job it is"

Foundation that's peniless?

"Foundation that's penniless?"

Basic Terminology

For Object Classes, MTF, and GoI, maybe include hyperlinks to the main pages for those things so it's easy for new users to navigate to if they're wanting to learn more.

general information that isn't relevant:

"general information which might not be relevant to you:"

so that you can vote, comment, and post your own works.

It might be a bit long, but I'd recommend adding something about the forums here. Sometimes people don't realise they have to join the site to use the forums¹. "so that you can vote, comment, use the forums, and post your own works."

what's going on can be an issue newcomers face.

"what's going on is an issue newcomers often face." (feels more friendly, more like "you have this issue and it's normal" rather than "this is a possibility we're covering even though it doesn't really happen a lot")

You'll find that anything in an article that isn't a link to a new page is expected to be read, so don't rush through articles!

"You'll find that everything included in an article or guide (excluding links to separate pages, but including tabviews and collapsibles) is expected to be read, so make sure not to rush through reading them."

written as far back as 2010.

Is this date correct? I'm unsure on the history but I swear it was 2008.

comment on existing ones, vote,

"vote and comment on existing articles,"

Should go without saying, but still; Don't be an asshole to your fellow members

"This should go without saying, but still. Don't be an asshole to your fellow members"

telling people "your article sucks balls" without explaining why it sucks balls

This is hilarious. However, as funny as it is and as much as I would like to be able to say it sometimes, I would personally not consider "your article sucks balls" to be acceptable critique even if the critter did explain why, and I don't think the Criticism Policy does either. My concern is that the joke may go over people's heads here, and they may think they can be vehement towards others' work as long as they explain why and aren't a dick about the author. I suppose the sentence after this one clears it up a bit, but people do not read very well on this website. Minor concern, of course, but worth bringing up.

Don't do those.

Perhaps mention something here about how users can ask staff if they aren't sure whether they're violating/close to violating a rule or guideline. I think it was mentioned earlier in the Guide For Newcomers, but worth repeating.

changes to another person's article without their explicit consent which change the content in a non-dismissable manner.

"non-dismissable changes to another person's article without their explicit consent."

On here you can see mostly anything related to staff's work,

"On here you can see things related to staff's work," Perhaps "most things" would work too. I don't think "mostly anything" makes sense.

05command

Capital "C" for consistent spelling.

Additionally, if at any point you feel like you want to join staff to help maintain the site, there are semi-frequent staff recruitment threads on the site forums which you are more than welcome to sign up for.

"Additionally, if at any point you feel like you want to join staff to help maintain the site, some teams are invite-only, but for others there are semi-frequent staff recruitment threads on the site forums which you are more than welcome to sign up for." I'm sure this is just my personal opinion, but I think something should be included here about not asking to be staff straight off the bat. "It's recommended that you spend some time in the onsite community before asking to be staff so you're aware of how the site functions first" or something.

a cohesive detailing of every concert Bruce Springsteen has ever done, for some reason…

"a cohesive detailing of every concert Bruce Springsteen has ever done for some reason…" Also, do you mean "cohesive" or "comprehensive"?

platform, (if you have any issues with that go to the official chatrooms and ask around,) and then

"platform², and then" If you don't want to use footnotes in this guide, use brackets without also using commas.

Wikidot is A Platform

Is there a reason the "is" isn't capitalised? I also think this section should be moved to before the previous one because it mentions that wikidot does not like emails with numbers in them, and also I do not believe very many people will read this section if it's after the previous one. It has a bunch of really useful information which answers common newbie questions ("why isn't wikidot sending me the email?" and "what is the sandbox?" and "why can i not use the sandbox when i'm a member of the mainsite?") but people won't read it once they've been told how to apply.

explained in the chat guide

I think put the link to the chat guide here, rather than in "official chats" in the line above.

Welcome to the site.

"Welcome to the site!" Also imo it doesn't need two line breaks; I think one would be fine unless you plan on having a title there as well.

Also, this is an introduction to writing. If you're more interested in sharing art, see How to Post Your Art to the SCP Wiki.

"Also, this is an introduction to writing specifically, so if you're more interested in sharing art, please see How to Post Your Art to the SCP Wiki."

It is better to fail than to have never tried at all

Hmm. Yes, but also it's best not to encourage authors to throw their drafts at the mainsite. At this point in the guide, you haven't mentioned any alternative to posting straight to the mainsite and you don't for quite some time. My worry is that this may come across as "coldpost until you succeed, because it doesn't matter if you fail" rather than "if you make the mistake of coldposting and have a work go into deletion initially (or at any point) that's okay because there are ways to improve such as using the sandbox and getting critique, and you won't be penalised for having a deleted article". Nobody is going to penalise a newbie for having an article go into deletion, it happens, but I don't think it should be written that failure is something that happens to everyone here because it doesn't. It can happen to anyone, but if users get crit and follow the process properly it's far less likely to happen to them and they're far less likely to be discouraged from writing than if they throw stuff on the mainsite and hope it'll stick this time.

you must get your idea greenlighted

"greenlit" is preferred I believe. It's also not a necessity to be greenlit unless a user wants to use the Draft Forum, but I'm hoping that people curious about the process will read the Greenlighting Policy. It might also be a good idea to write "(not your draft)" after "idea". Common newbie misconceptions etc etc.

at least two experienced authors

Not all authors have greenlight privileges and not everybody with greenlight privileges is an author. "experienced users" or "experienced reviewers" with a link to this: https://scp-wiki.wikidot.com/forum/t-9804362/so-you-want-to-be-a-concept-reviewer#post-4183926 (which shows who can give greenlights) would be better.

Once you've made a sandbox page and gotten greenlighted, you're good to go!

This is pretty vague. Good to post? Good to seek crit? Good to start writing a draft?

and/or Site Critique staff

While you probably mean "mainsite critique staff", Site Crit is its own team and its eventual goal is separate from Forum Crit's so this should probably say "Critique Staff" or "experienced reviewers".

The best place to ask is the official drafts critique forum

I would add something here about needing greenlights and/or making sure users read the sticky threads before posting to the draft forum (or any forum).

create an author post under your page's discussion thread.

Maybe add something about reserving space for author posts. "If you plan to make an author post, it's best to make a post in your page's discussion with the text "reserved" or "r" and then edit it later. This is to make sure that your author post is at the top of the discussion. Author posts can say anything you want within reason, but are most often used to talk briefly about your article and to thank your reviewers."

you can PM a member of the Butterfly Squad³

Re: the footnote in particular, not all Butterflies are staff members. "Experienced reviewers" works better. We also crit more than drafts, so "drafts and ideas" or "articles" or just "specialize in critique/ing" is more accurate.

If you think you can do well in critique, you can ask to do a draft exchange, where you and another user swap drafts and critique each other's work.

"You can also ask to do a crit exchange, where you and another user swap drafts or ideas and critique each other's work. You don't have to be an experienced critter to do this, but it's best to read [link to the forum sticky threads on how to give crit] these threads first if you're unsure how to start."

grammar, tone and pacing

Oxford comma lol. "grammar, tone, and pacing"