update files

README.md

@@ -32,35 +32,62 @@ Sometimes  the output wav file of a text file line is longer than necessary, con
 
  In order to detect which wave files are generated having that problem, the ratio of _character count of line / duration of audio file_ is calculated. This ratio helps us roughly to estimate which lines were rendered with errors.
 
-The lines that _possibly_ present this problem are written down in the error.tsv that is generated. After the end of  all the lines, 
+The lines that _possibly_ present this problem are written down in the errors.tsv that is generated. After the end of  all the lines, the lines written down in the tsv file get re-rendered.
 
- * the lines written down in the tsv file get re-rendered. Many times this alone is enough.
- * After that each line one by one can be examined. The user can 
+ Many times this alone is enough.
 
-      1.__Play__ the respective audio file
-
-     2.__Re-render__ the line, making minor changes(like e.g. putting a fullstop at the end of the line)
-
-
-    3.__Trim the clutter__ that exists at the end of audio file, anything that exists after half a second of detected silence.
-
-     4.__Split__ render the line text in two batches, that will be concatenated after(useful in long sentences)
-
-    5.__Edit__ the respective audio file with a wave editor(e.g._Audacity)
-
-    6.__Remove__ the respective audio file directly.
-
-    7.By hiting __Keep__ the user can accept the audio file as is, or after correcting it, and proceed to the next.
+After that each line one by one can be examined. The user is presented with *a few options* for each line: 
 
 ---
 
 ![5.png](screenshots/5.png)
 
 
-After that, the audio files from all the lines will be concatenated into one.
+
 
 ---
 
+These optios include:
+
+  *    **Play** the respective audio file
+
+
+  *    __Re-render__ the line, making minor changes(like e.g. putting a fullstop at the end of the line)
+
+
+---
+
+![6.png](screenshots/6.png)
+
+
+
+
+---
+
+  *   __Trim the clutter__ that exists at the end of audio file, anything that exists after half a second of detected silence.
+  * 
+
+  *   __Split render__ the line text in two batches, that will be concatenated after(useful in long sentences)
+
+---
+
+![7.png](screenshots/7.png)
+
+
+
+
+---
+
+
+  *   __Edit__ the respective audio file with a wave editor(e.g._Audacity)
+
+  *   __Remove__ the respective audio file directly.
+
+  *   By hiting __Keep__ the user can accept the audio file as is, or after correcting it, and proceed to the next.
+
+
+**After that, the audio files from all the lines will be concatenated into one.**
+
 ### II. SED SCRIPT
 
 sapofonetix.sed is a script that substitutes words that get mispelled  with other letter combinations, that have the right pronunciation result, e.g. 
@@ -120,6 +147,6 @@ ___
 
 ### Sapo-fix.sh
 
-Sapo-fish.sh is the error-correcting routine included in Sapo.sh, that can be run on its own, when the user wants to correct the lines detected and written in error.tsv. 
+Sapo-fish.sh is the error-correcting routine included in Sapo.sh, that can be run on its own, when the user wants to correct the lines detected and written in errors.tsv. 
 
-The user can also edit any line he wishes, just by entering in a line of terror.tsv the respective line number, wav number, and then run Sapo-fix.sh.
+The user can also edit any line he wishes, just by entering in a line of errors.tsv the respective line number, wav number, and then run Sapo-fix.sh.

sapo-fix.sh

@@ -42,7 +42,7 @@ do
 $TEXT_TO_CORRECT 
 							 
 -What would you like to do?" \
-						--window-icon=$HOME/git/sapo/sapo.png
+						--window-icon=$HOME/git/sapo/sapo-fix.png
 		case $? in 
 		 0) GO=true 
 		 ;;