Breaking up the editing into two tasks, silent and aloud, greatly helped the whole process. The more I experiment with it, the more effectively I can correct mistakes. Silent editing has become a mechanical process where the mistakes are removed systematically as they are found, like running the text through a sieve. Out-loud editing is much more lively. I get into the process and add emotion even though it’s not necessary. It can be fun, and I look forward to the next pass of editing and recording.
Putting a time gap between the silent and out-loud steps has proven useful. If the text can settle in my mind after a silent editing session, the next phase allows a clean revision of the rougher passages, and they become natural sounding.
The pace of editing has increased, or the length of chapters has decreased. At first, I could edit one chapter per day, but that has become two. This week, chapters eighteen through twenty-four were edited.
Here is a link to the text as it is being edited. Charged: DesertIrish partially edited
Putting a time gap between the silent and out-loud steps has proven useful. If the text can settle in my mind after a silent editing session, the next phase allows a clean revision of the rougher passages, and they become natural sounding.
The pace of editing has increased, or the length of chapters has decreased. At first, I could edit one chapter per day, but that has become two. This week, chapters eighteen through twenty-four were edited.
Here is a link to the text as it is being edited. Charged: DesertIrish partially edited
Charged: DesertIrish
The rest of the weekly summaries have been arranged by date.
Disclaimer for http://24hourengineer.blogspot.com/
This disclaimer must be intact and whole. This disclaimer must be included if a project is distributed.
All information in this blog, or linked by this blog, is not to be taken as advice or solicitation. Anyone attempting to replicate, in whole or in part, is responsible for the outcome and procedure. Any loss of functionality, money, property or similar, is the responsibility of those involved in the replication.
All digital communication regarding the email address 24hourengineer@gmail.com becomes the intellectual property of Brian McEvoy. Any information contained within these messages may be distributed or retained at the discretion of Brian McEvoy. Any email sent to this address, or any email account owned by Brian McEvoy, cannot be used to claim property or assets.
Comments to the blog may be utilized or erased at the discretion of the owner. No one posting may claim property or assets based on their post.
This blog, including pictures and text, is copyright to Brian McEvoy.
This disclaimer must be intact and whole. This disclaimer must be included if a project is distributed.
All information in this blog, or linked by this blog, is not to be taken as advice or solicitation. Anyone attempting to replicate, in whole or in part, is responsible for the outcome and procedure. Any loss of functionality, money, property or similar, is the responsibility of those involved in the replication.
All digital communication regarding the email address 24hourengineer@gmail.com becomes the intellectual property of Brian McEvoy. Any information contained within these messages may be distributed or retained at the discretion of Brian McEvoy. Any email sent to this address, or any email account owned by Brian McEvoy, cannot be used to claim property or assets.
Comments to the blog may be utilized or erased at the discretion of the owner. No one posting may claim property or assets based on their post.
This blog, including pictures and text, is copyright to Brian McEvoy.
Comments
Post a Comment