xforms-development
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [XForms] [PATCH] Fix two typos in documentation


From: Jens Thoms Toerring
Subject: Re: [XForms] [PATCH] Fix two typos in documentation
Date: Thu, 1 Oct 2015 21:37:43 +0200
User-agent: Mutt/1.5.21 (2010-09-15)

Hi Vitaly.

On Thu, Oct 01, 2015 at 03:51:47PM +0300, Vitaly Sinilin wrote:
> ---
>  doc/part1_getting_started.texi |    4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/doc/part1_getting_started.texi b/doc/part1_getting_started.texi
> index 0cdd0d9..7685164 100644
> --- a/doc/part1_getting_started.texi
> +++ b/doc/part1_getting_started.texi
> @@ -237,11 +237,11 @@ have exactly the same effect.
>  The above program only shows one of the event handling methods
>  provided by the library. The direct method of event handling shown is
>  appropriate for simple programs. But, obviously, already for a program
> -with just a few nmore objects it would become rather tedious to have
> +with just a few more objects it would become rather tedious to have
>  to check each time @address@hidden()}} returns each of those
>  objects to find out which of them was responsible and react
>  accordingly. Utilizing object callback functions is then typically
> -much easier and thus os strongly recommended.
> +much easier and thus is strongly recommended.
>  
>  We demonstrate the use of object callbacks using the previous example
>  with some modifications so that event processing via callbacks is
> -- 
> I'm not subscribed to the list.

Thank you very much, the typos are fixed in the sources for the
next version. And further posts by you will be accepted to the
mailing list without delay (but you won't get any mails from it
as long as you don't subscribe, of course).

                            Best regards, Jens
-- 
  \   Jens Thoms Toerring  ________      address@hidden
   \_______________________________      http://toerring.de



reply via email to

[Prev in Thread] Current Thread [Next in Thread]