Re: Documentation improvement patch

2024-10-07 Thread Oleg Sibiryakov
Thank you, Daniel. -- Oleg Sibiryakov On 02.10.2024 15:58, Daniel Gustafsson wrote: On 2 Oct 2024, at 10:09, Oleg Sibiryakov wrote: Thank you for your kind feedback! I will take due note of the comments in the next documentation patches as well. I have made all the changes as per your feedb

Re: Documentation improvement patch

2024-10-02 Thread Daniel Gustafsson
> On 2 Oct 2024, at 10:09, Oleg Sibiryakov wrote: > > Thank you for your kind feedback! I will take due note of the comments in the > next documentation patches as well. > > I have made all the changes as per your feedback and also corrected paragraph > reflow. > > The third version of the pa

Re: Documentation improvement patch

2024-10-02 Thread Oleg Sibiryakov
01.10.2024 11:59, Daniel Gustafsson wrote: On 1 Oct 2024, at 10:04, Oleg Sibiryakov wrote: Here is a kind reminder of a small documentation improvement patch, which we started discussing a month ago. I removed all the controversial points touched upon in this thread. Please, take a look once

Re: Documentation improvement patch

2024-10-01 Thread Oleg Sibiryakov
Dear all, Here is a kind reminder of a small documentation improvement patch, which we started discussing a month ago. I removed all the controversial points touched upon in this thread. Please, take a look once again at your convenience. The patch shall be applied to the master branch

Re: Documentation improvement patch

2024-10-01 Thread Daniel Gustafsson
> On 1 Oct 2024, at 10:04, Oleg Sibiryakov wrote: > Here is a kind reminder of a small documentation improvement patch, which we > started discussing a month ago. > > I removed all the controversial points touched upon in this thread. Please, > take a look once again at you

Re: Documentation improvement patch

2024-09-13 Thread Oleg Sibiryakov
Here is a patch without the builtin/built-in corrections (find attached). But I still believe the issue should be discussed further. We actually have two options: it is either a spelling mistake (since built-in should written with a hyphen), or we miss the tag (since it is actually also a valu

Re: Documentation improvement patch

2024-09-11 Thread Peter Eisentraut
On 10.09.24 15:02, Daniel Gustafsson wrote: On 10 Sep 2024, at 13:46, Oleg Sibiryakov wrote: 1. Since we do not want to use here, I suggest we hyphenate it as "built-in". What's your take on it? I think that's the right choice given the hyphenation used in the rest of the docs. There are

Re: Documentation improvement patch

2024-09-10 Thread Daniel Gustafsson
> On 10 Sep 2024, at 13:46, Oleg Sibiryakov wrote: > 1. Since we do not want to use here, I suggest we hyphenate it as > "built-in". What's your take on it? I think that's the right choice given the hyphenation used in the rest of the docs. There are a few more places on that same page which

Re: Documentation improvement patch

2024-09-10 Thread Oleg Sibiryakov
Thank you for your feedback. 1. Since we do not want to use here, I suggest we hyphenate it as "built-in". What's your take on it? 2. Leaving not-null is fine. -- Oleg Sibiryakov On 06.09.2024 16:20, Daniel Gustafsson wrote: On 5 Sep 2024, at 11:33, Oleg Sibiryakov wrote: Dear all, I have

Re: Documentation improvement patch

2024-09-06 Thread Daniel Gustafsson
> On 5 Sep 2024, at 11:33, Oleg Sibiryakov wrote: > > Dear all, > I have prepared a patch containing some minor inconsistencies in the > documentation. Please, take a look. > The inconsistencies were noticed by: Ekaterina Kiryanova, Elena Indrupskaya, > Maxim Yablokov, Anna Uraskova, Elena Kara

Documentation improvement patch

2024-09-05 Thread Oleg Sibiryakov
Dear all, I have prepared a patch containing some minor inconsistencies in the documentation. Please, take a look. The inconsistencies were noticed by: Ekaterina Kiryanova, Elena Indrupskaya, Maxim Yablokov, Anna Uraskova, Elena Karavaeva, and me. We will be looking forward to your feedback