12212 typos in some section 3tecla man pages

*** 57,68 ****
         non-blocking server mode requires an initial call to gl_io_mode().
  
     Server I/O Mode
         In non-blocking server I/O mode, the application is required to have an
         event loop that calls gl_get_line() whenever the terminal file
!        descriptor can perform the type I/O that gl_get_line() is waiting for.
!        To determine which type of I/O gl_get_line() is waiting for, the
         application calls the gl_pending_io() function.  The return value is
         one of the following two enumerated values.
  
         GLP_READ
                      gl_get_line() is waiting to write a character to the
--- 57,68 ----
         non-blocking server mode requires an initial call to gl_io_mode().
  
     Server I/O Mode
         In non-blocking server I/O mode, the application is required to have an
         event loop that calls gl_get_line() whenever the terminal file
!        descriptor can perform the type of I/O that gl_get_line() is waiting
!        for. To determine which type of I/O gl_get_line() is waiting for, the
         application calls the gl_pending_io() function.  The return value is
         one of the following two enumerated values.
  
         GLP_READ
                      gl_get_line() is waiting to write a character to the
*** 69,79 ****
                      terminal.
  
  
         GLP_WRITE
                      gl_get_line() is waiting to read a character from the
!                     keyboad.
  
  
  
         If the application is using either the select(3C) or poll(2) function
         to watch for I/O on a group of file descriptors, then it should call
--- 69,79 ----
                      terminal.
  
  
         GLP_WRITE
                      gl_get_line() is waiting to read a character from the
!                     keyboard.
  
  
  
         If the application is using either the select(3C) or poll(2) function
         to watch for I/O on a group of file descriptors, then it should call
*** 338,349 ****
                    statements are always executed with all of our signals
                    blocked.
  
             10.    Reinstate the signal handlers that were displaced in step 5.
  
!            11.    Check wether a signal was caught, by checking the file-scope
!                   variable that the signal handler records signal numbers in.
  
             12.    If a signal was caught, send this signal to the application
                    again and unblock only this signal so that it invokes the
                    signal handler which was just reinstated in step 10.
  
--- 338,350 ----
                    statements are always executed with all of our signals
                    blocked.
  
             10.    Reinstate the signal handlers that were displaced in step 5.
  
!            11.    Check whether a signal was caught, by checking the file-
!                   scope variable that the signal handler records signal
!                   numbers in.
  
             12.    If a signal was caught, send this signal to the application
                    again and unblock only this signal so that it invokes the
                    signal handler which was just reinstated in step 10.
  
*** 365,375 ****
         respond to the SIGINT user-interrupt signal by aborting the current
         input line. This can be accomplished in non-blocking server-I/O mode by
         not calling gl_handle_signal() when this signal is caught, but by
         calling instead the gl_abandon_line() function. This function arranges
         that when gl_get_line() is next called, it first flushes any pending
!        output to the terminal, discardes the current input line, outputs a new
         prompt on the next line, and finally starts accepting input of a new
         input line from the user.
  
     Signal Safe Functions
         Provided that certain rules are followed, the gl_normal_io(),
--- 366,376 ----
         respond to the SIGINT user-interrupt signal by aborting the current
         input line. This can be accomplished in non-blocking server-I/O mode by
         not calling gl_handle_signal() when this signal is caught, but by
         calling instead the gl_abandon_line() function. This function arranges
         that when gl_get_line() is next called, it first flushes any pending
!        output to the terminal, discards the current input line, outputs a new
         prompt on the next line, and finally starts accepting input of a new
         input line from the user.
  
     Signal Safe Functions
         Provided that certain rules are followed, the gl_normal_io(),
*** 433,438 ****
         cpl_complete_word(3TECLA), ef_expand_file(3TECLA), gl_get_line(3TECLA),
         libtecla(3LIB), pca_lookup_file(3TECLA), attributes(5), tecla(5)
  
  
  
!                                  June 1, 2004               GL_IO_MODE(3TECLA)
--- 434,439 ----
         cpl_complete_word(3TECLA), ef_expand_file(3TECLA), gl_get_line(3TECLA),
         libtecla(3LIB), pca_lookup_file(3TECLA), attributes(5), tecla(5)
  
  
  
!                                January 18, 2020             GL_IO_MODE(3TECLA)