docs: reduce use of "very"

"Very" should be avoided in most texts. If intensifiers are needed, try
find better words instead.

Closes #7936
This commit is contained in:
Daniel Stenberg 2021-11-01 13:43:11 +01:00
parent e05c08687f
commit 92efb3db7e
No known key found for this signature in database
GPG key ID: 5CC908FDB71E12C2
51 changed files with 232 additions and 236 deletions

View file

@ -2,7 +2,7 @@
Source code that has a common style is easier to read than code that uses
different styles in different places. It helps making the code feel like one
single code base. Easy-to-read is a very important property of code and helps
single code base. Easy-to-read is an important property of code and helps
making it easier to review when new things are added and it helps debugging
code when developers are trying to figure out why things go wrong. A unified
style is more important than individual contributors having their own personal
@ -56,10 +56,10 @@ introduced in the C standard until C99. We use only __/* comments */__.
## Long lines
Source code in curl may never be wider than 79 columns and there are two
reasons for maintaining this even in the modern era of very large and high
reasons for maintaining this even in the modern era of large and high
resolution screens:
1. Narrower columns are easier to read than very wide ones. There's a reason
1. Narrower columns are easier to read than wide ones. There's a reason
newspapers have used columns for decades or centuries.
2. Narrower columns allow developers to easier show multiple pieces of code
@ -154,8 +154,8 @@ if(!ptr)
## New block on a new line
We never write multiple statements on the same source line, even for very
short if() conditions.
We never write multiple statements on the same source line, even for short
if() conditions.
```c
if(a)