diff options
Diffstat (limited to 'src')
| -rw-r--r-- | src/common/address.c | 2 | ||||
| -rw-r--r-- | src/or/main.c | 2 | ||||
| -rw-r--r-- | src/or/or.h | 4 |
3 files changed, 4 insertions, 4 deletions
diff --git a/src/common/address.c b/src/common/address.c index 69a80986ed..061bb7e724 100644 --- a/src/common/address.c +++ b/src/common/address.c @@ -1784,7 +1784,7 @@ tor_addr_port_parse(int severity, const char *addrport, } /** Given an address of the form "host[:port]", try to divide it into its host - * ane port portions, setting *<b>address_out</b> to a newly allocated string + * and port portions, setting *<b>address_out</b> to a newly allocated string * holding the address portion and *<b>port_out</b> to the port (or 0 if no * port is given). Return 0 on success, -1 on failure. */ int diff --git a/src/or/main.c b/src/or/main.c index c8b1283974..0ab8f10a4b 100644 --- a/src/or/main.c +++ b/src/or/main.c @@ -1301,7 +1301,7 @@ static periodic_event_item_t periodic_events[] = { /* These are pointers to members of periodic_events[] that are used to * implement particular callbacks. We keep them separate here so that we * can access them by name. We also keep them inside periodic_events[] - * so that we can implement "reset all timers" in a reasaonable way. */ + * so that we can implement "reset all timers" in a reasonable way. */ static periodic_event_item_t *check_descriptor_event=NULL; static periodic_event_item_t *fetch_networkstatus_event=NULL; static periodic_event_item_t *launch_descriptor_fetches_event=NULL; diff --git a/src/or/or.h b/src/or/or.h index 89c539817f..6b5bd86761 100644 --- a/src/or/or.h +++ b/src/or/or.h @@ -2333,7 +2333,7 @@ typedef struct microdesc_t { curve25519_public_key_t *onion_curve25519_pkey; /** Ed25519 identity key, if included. */ ed25519_public_key_t *ed25519_identity_pkey; - /** As routerinfo_t.ipv6_add */ + /** As routerinfo_t.ipv6_addr */ tor_addr_t ipv6_addr; /** As routerinfo_t.ipv6_orport */ uint16_t ipv6_orport; @@ -2351,7 +2351,7 @@ typedef struct microdesc_t { * Specifically, a node_t is a Tor router as we are using it: a router that * we are considering for circuits, connections, and so on. A node_t is a * thin wrapper around the routerstatus, routerinfo, and microdesc for a - * single wrapper, and provides a consistent interface for all of them. + * single router, and provides a consistent interface for all of them. * * Also, a node_t has mutable state. While a routerinfo, a routerstatus, * and a microdesc have[*] only the information read from a router |