Skip to content

Commit f3f7312

Browse files
authored
Merge pull request #1838 from a-andre/typo
Fix some typos
2 parents 7354439 + 9b1d5c5 commit f3f7312

File tree

3 files changed

+6
-6
lines changed

3 files changed

+6
-6
lines changed

doc/socket_loop.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ int picoquic_packet_loop_v2(picoquic_quic_t* quic,
3838
```
3939

4040
The loop will execute,
41-
calling the Picoquic Netowrking API functions `picoquic_prepare_next_packet_ex`
41+
calling the Picoquic Networking API functions `picoquic_prepare_next_packet_ex`
4242
to ask the stack whether packets are ready to be sent and
4343
`picoquic_incoming_packet_ex` when packets are received from the network.
4444

@@ -101,8 +101,8 @@ It exposes a series of callback events:
101101
it wants to be called for a time check before the loops waits for timers or incoming packets.
102102
* `picoquic_packet_loop_after_receive`: Called after packets have been received, enabling the application
103103
to perform picoquic API calls triggered by the received data.
104-
* `picoquic_packet_loop_after_send`: Called after packets have been received, enabling the application
105-
to perform picoquic API calls triggered by the received data.
104+
* `picoquic_packet_loop_after_send`: Called after packets have been sent, enabling the application
105+
to perform picoquic API calls triggered by the sent data.
106106
* `picoquic_packet_loop_port_update`: Provides a "loopback" socket address corresponding to the main
107107
socket. Can be used to learn the port number associated with that socket.
108108
* `picoquic_packet_loop_time_check`: Called before the packet loop starts waiting for a new packet or a

doc/usage.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,12 +10,12 @@ On Linux after building, the following executables are available in the project
1010
## HTTP Client and Server Usage
1111
* client: ./picoquicdemo servername serverportnumber HTTPpath
1212
* downloaded files will be in current directory. use -o for another folder
13-
* exemple: ./picoquicdemo -o ../received 192.0.2.1 4433 index.html
13+
* example: ./picoquicdemo -o ../received 192.0.2.1 4433 index.html
1414
* server: ./picoquicdemo -p portnumber
1515
* -p argument tells the program that it is acting as a server
1616
* HTML root folder is current directory by default. use -w for another folder
1717
* keys and certs are specified by -k and -c. See -h for more details.
18-
* exemple: ./picoquicdemo -w ../htmlroot -p 4433
18+
* example: ./picoquicdemo -w ../htmlroot -p 4433
1919
* additional useful information for HTTP usage is available at:
2020
* [Without DNS Names Or Certs](https://github.com/private-octopus/picoquic/wiki/Testing-without-DNS-names-or-Certificates)
2121
* [Certs Using Lets Encrypt](https://github.com/private-octopus/picoquic/wiki/Import-key-and-cert-on-server-from-Let's-encrypt)

picoquic/quicctx.c

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1431,7 +1431,7 @@ int64_t picoquic_get_next_wake_delay(picoquic_quic_t* quic,
14311431
* future, which implies the time in microseconds is less than 2^62.
14321432
* The delay MAX is lower than INT64_MAX, i.e., 2^63.
14331433
* The next wake time is often set to UINT64_MAX, and might sometime
1434-
* me just under that value, so we make sure to avoid integer
1434+
* be just under that value, so we make sure to avoid integer
14351435
* overflow in the computation.
14361436
*/
14371437
uint64_t next_wake_time = picoquic_get_next_wake_time(quic, current_time);

0 commit comments

Comments
 (0)