TIP: Click on subject to list as thread! ANSI
echo: trek_creative
to: All
from: maira manno
date: 2003-07-26 20:08:28
subject: Re: [trekcreative] CHURCHILL 1.1 part one.

To: 
From: "maira manno" 
Reply-To: trekcreative{at}yahoogroups.com

------=_NextPart_000_0008_01C353B1.ADE26CC0
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

While your piece is a fairly straightforward, competently executed intro,
y= ou lose more than a few points because there are more than half a dozen
edi= torial errors in just that one small sample... and I'm not counting
the stu= ff that simply marks you as a citizen of the British Empire
vis-a-vis a nit= picky Yank like me.

---------------------------------------------------------------------------=
-----

"He knew that most of his life for five years would be spent [here] and the=
 idea filled him with a strange sense of pride."

You dropped the bracketed word, I daresay.

"Lieutenant, are the microfractures bad enough that you will need to
replac= e those deck plates?".

The period at the end of the sentence is superfluous.

"'I'll have to replace it then go over any plating from the same
shipment i= ncase the flaw is common to all of them'.

"In case" is not one word.

"Brand smiled, he knew that Lieutenant Tabitha Burke, informally known
to h= er friends as Tabby, was on her first tour of duty as Chief Engineer
and sh= e was determined nothing was wrong."

"Smiled" should be followed by a period, semi-colon or even a
full colon. A=
 comma is the one piece of punctuation giving insufficient pause there. In =
addition, that third "was" should probably read "would
go," instead.

"'Understood, Contact Starfleet Command if you need any more
engineering cr= ew'."

"Contact" should be lower case in the above sentence; and, again,
the comma=
 before it is insufficient pause. It requires a period or semi-colon.

He was going to be commanding a untried ship and crew into unknown
territor= y, far beyond the range of instantaneous subspace
communication.=20

That should be "an untried ship."

The crew would essentially be on it's own should they encounter anything da= ngerous.

"It's" should be "its" in the above sentence.

---------------------------------------------------------------------------=
-----

Seven paragraphs... nine errors. While none are particularly damning,
toget= her they make the excerpt look sloppy and unprofessional. I'd love
to read = Churchill... but I shan't if I have to plow through unedited
prose.

I hope you're not offended; you did ask for feedback.
------=_NextPart_000_0008_01C353B1.ADE26CC0
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable










While your piece
is a fairly=20
straightforward, competently executed intro, you lose more than a =
;few=20
points because there are more than half a dozen editorial
errors = in=20
just that one small sample... and I'm not counting the stuff that
simp= ly=20
marks you as a citizen of the British Empire vis-a-vis
a nitpicky = Yank=20
like me.



"He knew that most of his
life for five ye=
ars would=20
be spent [here] and the idea filled him with a strange sense of=20
pride."
 
You dropped the
bracketed word, I=
=20
daresay.
 
"Lieutenant, are the
microfractures bad en=
ough that=20
you will need to replace those deck plates?".
 
The period at
the end of the sente=
nce is=20
superfluous.
 
"'I=92ll have to replace
it then go over a=
ny plating=20
from the same shipment incase the flaw is common to all of them'.
 
"In
case" is not one=20
word.
 
"Brand smiled, he knew
that Lieutenant Tab=
itha=20
Burke, informally known to her friends as Tabby, was on her first tour of d= uty=20
as Chief Engineer and she was determined nothing was
wrong."
 
"Smiled" should be followed by a p=
eriod,=20
semi-colon or even a full colon. A comma is the one piece of punctuation gi= ving=20
insufficient pause there. In addition, that third "was" should
probably rea= d=20
"would go," instead.
 
"'Understood, Contact
Starfleet Command if=
 you need=20
any more engineering crew'."
 
"Contact" should be lower case in =
the above=20
sentence; and, again, the comma before it is insufficient pause.
It=20 requires a period or
semi-colon.
 
He was going to be commanding
a untried sh=
ip and=20
crew into unknown territory, far beyond the range of instantaneous subspace=
=20
communication. 
 
That should be
"an untrie=
d=20
ship."
 
The crew would essentially be
on it=92s ow=
n should=20
they encounter anything dangerous.
 
"It's"
should be "its" in the abov=
e=20
sentence.



Seven
paragraphs... nine =
errors.=20
While none are particularly damning, together they
make the excerp= t=20
look sloppy and unprofessional. I'd love to read
Churchill... but = I=20
shan't if I have to plow through unedited
prose.
 
I hope you're
not offended; you di=
d ask for=20
feedback.






Yahoo! Groups Spons=
or


ADVERTISEMENThttp://rd.yahoo.com/M=3D194081.3551198.4824677.1261774/=
D=3Degroupweb/S=3D1705019987:HM/A=3D1663535/R=3D0/SIG=3D11ps6rfef/*http://w=
ww.ediets.com/start.cfm?code=3D30504&media=3Datkins"
alt=3D""> 

3D""http://us.adserver.yahoo.=
com/l?M=3D194081.3551198.4824677.1261774/D=3Degroupmail/S=3D:HM/A=3D1663535=
/rand=3D260928203">







Star Trek; The E-mail Commands

Post message: trekcreative{at}yahoogroups.com Subscribe:
trekcreative-subscribe{at}yahoogroups.com Unsubscribe:
trekcreative-unsubscribe{at}yahoogroups.com List owner:
trekcreative-owner{at}yahoogroups.com Get Digest:
trekcreative-digest{at}yahoogroups.com Web only: 
trekcreative-nomail{at}yahoogroups.com Normal:
trekcreative-normal{at}egroups.com



Your use of Yahoo! Groups is subject to the http://docs.yaho=
o.com/info/terms/">Yahoo! Terms of Service.




------=_NextPart_000_0008_01C353B1.ADE26CC0--

--- BBBS/NT v4.01 Flag-5
 * Origin: Email Gate (1:379/100)
SEEN-BY: 633/267 270
@PATH: 379/100 101 1 10/345 106/1 2000 633/267

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.