comparison doc/cmdline.rst @ 33:d28d94bf6b39

doc update

 
 1. the detector tolerates phases of silence of up to 0.3 second (300 ms) within an audio activity (also referred to as acoustic event):
 
 .. figure:: figures/figure_1.png
     :align: center
-    :alt: alternate text
+    :alt: Output from a detector that tolerates silence periods up to 300 ms
     :figclass: align-center
+    :scale: 40 %
 
 2. the detector splits an audio activity event into many activities if the within activity silence is over 0.2 second:
 
 .. figure:: figures/figure_2.png
     :align: center
-    :alt: alternate text
+    :alt: Output from a detector that tolerates silence periods up to 200 ms
     :figclass: align-center
+    :scale: 40 %
 
 
 ******************
 Command line usage
 ******************

     5
     00:00:09.510 --> 00:00:09.820
     Put some text here...
 
 
-2nd Practical use case example: build ab (very) basic voice control application
-###############################################################################
+2nd Practical use case example: build a (very) basic voice control application
+##############################################################################
 
 `This repository <https://github.com/amsehili/gspeech-rec>`_ supplies a bash script the can send audio data to Google's
 Speech Recognition service and get its transcription. In the following we will use **auditok** as a lower layer component
 of a voice control application. The basic idea is to tell **auditok** to run, for each detected audio activity, a certain
 number of commands that make up the rest of our voice control application.