mark writes:
>
> Bingo! Why pay for a professional editor when they can get that
> piggybacked on a much less costly service like a review?
So, approach it like anything else: if it needs work that you'd
be willing to do for pay, say that. e.g.:
It's difficult to evaluate this book for techn
Bingo! Why pay for a professional editor when they can get that piggybacked
on a much less costly service like a review?
--
mark
On Tue, Nov 19, 2013 at 11:53 AM, Greg Rundlett (freephile) <
g...@freephile.com> wrote:
> On Tue, Nov 19, 2013 at 11:44 AM, Seth Cohn wrote:
>
>> I did tech review f
On Tue, Nov 19, 2013 at 11:44 AM, Seth Cohn wrote:
> I did tech review for "Pro Drupal 7 for Windows Developers", and it
> was an ok experience.
>
>
Thanks.
> If you are doing editing of English, then the actual Editor isn't
> doing their job. You should be only doing tech review, not grammar,
I did tech review for "Pro Drupal 7 for Windows Developers", and it
was an ok experience.
If you are doing editing of English, then the actual Editor isn't
doing their job. You should be only doing tech review, not grammar,
etc.
Seth
On Tue, Nov 19, 2013 at 11:36 AM, Greg Rundlett (freephile)
I was asked by Packt publishing to do a technical book review (Apache SOLR
for Beginners)
I'm wondering if anyone else on the list has been a technical reviewer
before and would share your experience.
I was initially excited about the opportunity but it's become apparent, at
least in this case, t
