Welcome • User Guide
ToS • Privacy • Canary
Donate • Bugs • License

©2025 Poal.co

449

Once again, it's time for the FNGT!

If you don't know how this works, . That link will take you to another site to give you some additional information and tell you about some of our off-site features. That's also the site where we will host the weekly guitar threads, should Poal go down.

NOTE: That site is by invitation only. If you want an invite, and you're a regular participant, then just ask COF, Crazy, or myself.

If you do know what's going on, you probably don't need to click that link - but you may want to, to make sure you know of the other features, such as the archive or a separate forum that's invite only.

Remember, we are guests here on Poal. Let's act like it. If you're interested in supporting Poal, then .

**Once again, it's time for the FNGT!** If you don't know how this works, [click this link](https://fngt.gq/index.php?page=intro). That link will take you to another site to give you some additional information and tell you about some of our off-site features. That's also the site where we will host the weekly guitar threads, should Poal go down. **NOTE:** That site is by invitation only. If you want an invite, and you're a regular participant, then just ask COF, Crazy, or myself. If you do know what's going on, you probably don't need to click that link - but you may want to, to make sure you know of the other features, such as the archive or a separate forum that's invite only. Remember, we are guests here on Poal. Let's act like it. If you're interested in supporting Poal, then [you can donate](https://poal.co/donate).

(post is archived)

You are currently inside a comment thread.
Click here to see all the comments (244).
[–] • 0 pt

I usually try to be correct about such things as spelling and meaning, it seems that when the meaning gets changed it's somehow diluted. Now punctuation and capitalization, I don't really care about those in informal conversations

[–] • 0 pt

I usually aim for correctness in all things, but I can be pretty lax. I don't proofread comments on this site, for example. I ain't got time (nor care) for that shit. I do proof the stuff I write for my site. There aren't a whole lot of errors that make it through.

I cheat and use something I learned back in college. If you want to truly proofread something you've written, read it aloud. Reading it it aloud makes all the difference. You'll spot errors you'd not spot when reading it silently because your brain works differently when reading it aloud.

For example, if you'd read it aloud then you'd have noticed that I used "it" twice in one of my sentences.

[–] • 0 pt

LoL

That's a cool trick!

[–] • 0 pt

Indeed! I just used it. I wrote the article that's gonna be published on the 14th of this month, proofread it, and scheduled it for publication at 13:30 on 09/14/2021.

It's how I manage to get my articles done with so few errors. I actually also first share the links on Linux.org and they point out any mistakes - including tech mistakes. I pretty much never have a grammar issue of any note that gets caught by them. It's almost as good as having a third party (qualified third party) proofread for you.