CLEANUP: assorted typo fixes in the code and comments
This is 34th iteration of typo fixes
This commit is contained in:
parent
9e080bf375
commit
5fa29b8a74
|
@ -3104,7 +3104,7 @@ tune.quic.socket-owner { listener | connection }
|
|||
The "listener" value indicates that QUIC transfers will occur on the shared
|
||||
listener socket. This option can be a good compromise for small traffic as it
|
||||
allows to reduce FD consumption. However, performance won't be optimal due to
|
||||
a higher CPU usage if listeners are shared accross a lot of threads or a
|
||||
a higher CPU usage if listeners are shared across a lot of threads or a
|
||||
large number of QUIC connections can be used simultaneously.
|
||||
|
||||
tune.rcvbuf.client <number>
|
||||
|
|
|
@ -874,7 +874,7 @@ If EVENT_HDL_ASYNC_EVENT_DATA is not big enough to store your new
|
|||
event family struct, a compilation assert triggered by EVENT_HDL_CB_DATA
|
||||
will occur. In addition to this, an extra runtime BUG_ON will make
|
||||
sure the condition is met when publishing the event.
|
||||
The goal here is to force haproxy to fail explicitely so you know that
|
||||
The goal here is to force haproxy to fail explicitly so you know that
|
||||
something must be done on your side.
|
||||
|
||||
3.1 PUBLISHING AN EVENT
|
||||
|
|
|
@ -364,7 +364,7 @@ Core class
|
|||
Returns HAProxy core information. We can find information like the uptime,
|
||||
the pid, memory pool usage, tasks number, ...
|
||||
|
||||
These informations are also returned by the management socket via the command
|
||||
This information is also returned by the management socket via the command
|
||||
"show info". See the management socket documentation for more information
|
||||
about the content of these variables.
|
||||
|
||||
|
|
|
@ -154,7 +154,7 @@ encoded integer value |
|
|||
|
||||
- for other key type
|
||||
|
||||
The value length is annonced in table definition message
|
||||
The value length is announced in table definition message
|
||||
0 ....................
|
||||
value
|
||||
|
||||
|
|
|
@ -252,7 +252,7 @@
|
|||
| 4 | Heartbeat message. |
|
||||
+------------+--------------------------------------------------------+
|
||||
|
||||
About hearbeat messages: a peer sends heartbeat messages to peers it is
|
||||
About heartbeat messages: a peer sends heartbeat messages to peers it is
|
||||
connected to after periods of 3s of inactivity (i.e. when there is no
|
||||
stick-table to synchronize for 3s). After a successful peer protocol
|
||||
handshake between two peers, if one of them does not send any other peer
|
||||
|
|
|
@ -226,7 +226,7 @@ struct event_hdl_sub {
|
|||
/* --------------------------------------- */
|
||||
|
||||
/* user defined event types are listed here
|
||||
* please reflect any change in theses macros in the subtype map
|
||||
* please reflect any change in these macros in the subtype map
|
||||
* defined below that is used to perform string to event type and
|
||||
* event type to string conversions
|
||||
*/
|
||||
|
|
|
@ -1435,7 +1435,7 @@ static int quic_packet_encrypt(unsigned char *payload, size_t payload_len,
|
|||
/* Decrypt <pkt> packet using encryption level <qel> for <qc> connection.
|
||||
* Decryption is done in place in packet buffer.
|
||||
*
|
||||
* Returns 1 on sucess else 0.
|
||||
* Returns 1 on success else 0.
|
||||
*/
|
||||
static int qc_pkt_decrypt(struct quic_conn *qc, struct quic_enc_level *qel,
|
||||
struct quic_rx_packet *pkt)
|
||||
|
|
Loading…
Reference in New Issue