Sometimes the whole is greater than the sum of the parts. Nowhere is this more clear than when you look at a community of people. Collectively we have tremendous power to influence other people and we ought not underestimate that power. Given that, I'd like to make a general plea:
Please don't pile onto posts from new users!
What I mean is: if one person has commented on a post, don't add another comment if you can help it. Imagine today is your first day here and you get the following comments on your answer:
- Hi there and welcome to the site! You should  this answer and capitalize "Bible".
- This is more of a comment than an answer.
- I just wanted to welcome you to Biblical Hermeneutics. You have some good ideas, but I'd like know more about the number 42 symbolizing God's creation of earthworms. Can you flesh that out?
These aren't rude comments (well, except maybe the middle one), but impression of all three is that you aren't welcome here (despite being welcomed twice). Individually, the comments might be taken as helpful advice; together they can seem like nit-picking. Some posts have lots of problems and our instinct is to try and fix each one. Resist that impulse. Ideally new users will be welcomed with:
One comment that addresses the biggest issue.
Let's be honest: it's pretty unlikely that the biggest problem with a post is going to be a spelling error. The last (fake) comment above probably addressed the biggest problem with the (hypothetical) answer: nobody can figure out where the (purposely ridiculous) meaning assigned to 42 came from. So that should be the one comment on that post.
While we are at it, I should mention that in my experience, people love to know that other people have listened to their ideas and tried to understand them. So comments that engage with the content of the post rather it's the circumstances tend to leave a better impression. A new user can't really be expected to know the difference between answers and comments, but they can be expected to be interested in what they wrote. Asking interested questions is a simple communication trick that can go a long way toward making a new user (or anyone else) feel heard.
So how do you take care of nitpicky details? What can you do when there's already a comment on a new user's post? My rules of thumb are:
Ask questions about content, but edit for style.
When you edit, go big.
Editing is the #1 thing that sets Stack Exchange apart from every other Bible site around. I love editing. It's amazing to go through a post and fix all the things! You might think I'm fielding constant complaints about trampling on authorial intent or whatnot, but more often than not, people thank me for the edits. That's because I do more than just capitalize "Bible". I also:
- insert the text of the verse they quoted,
- italicize or bold important words and phrases,
- organize things under headings,
- fix their broken Markdown formatting,
- turn raw URLs into real links, and
- even find the blog post that supports the obscure connection between 42 and earthworms.
In the end, the post looks better. And if the author really meant to keep bible lower case, they can always re-edit the post. Be sure to note that further edits are possible in the change log, by the way. I went all-out editing the post and if I screwed up one little thing, it's not really a big deal: accidents happen. But if my edit had been just the nitpick, it would be all-too-clear what my agenda is. (Even if I don't have an agenda, it can look that way.)
We want to personally welcome new users, not collectively intimidate them.