Case (
case) wrote in
fandomsecrets2014-08-24 03:10 pm
[ SECRET POST #2791 ]
⌈ Secret Post #2791 ⌋
Warning: Some secrets are NOT worksafe and may contain SPOILERS.
01.

__________________________________________________
02.

__________________________________________________
03.

__________________________________________________
04.

__________________________________________________
05.

__________________________________________________
06.

__________________________________________________
07.

__________________________________________________
08.

__________________________________________________
09.

__________________________________________________
10.

Notes:
Secrets Left to Post: 03 pages, 058 secrets from Secret Submission Post #399.
Secrets Not Posted: [ 0 - broken links ], [ 0 - not!secrets ], [ 0 - not!fandom ], [ 0 - too big ], [ 0 - repeat ], [ 1 - posted twice ].
Current Secret Submissions Post: here.
Suggestions, comments, and concerns should go here.

Re: I was going to ask this, myself.
(Anonymous) 2014-08-25 02:02 am (UTC)(link)Sure, when I see an unbeta'd warning, a red flag goes off in my mind, but a few paragraphs are usually sufficient to determine if this is a problem. Quite often, it isn't, unless the writer just feels that the rules of grammar, spelling and punctuation do not apply to their masterpiece. No biggie, this is what the back button is for! :D
Personally I am very unforgiving of spelling mistakes, OOC characters or huge plot sinkholes etc. (which can happen far too easily when no friend has a chance to point out the problem tactfully), but I never prejudge based on an 'unbetaed' warning since most of the best authors I know do not use a beta, so.
Re: I was going to ask this, myself.
I find the ones who do warn that their work is unbeta'd know their spelling and grammar is not perfect and the warning is partly about that.