summaryrefslogtreecommitdiff
path: root/docs/ref
diff options
context:
space:
mode:
Diffstat (limited to 'docs/ref')
-rw-r--r--docs/ref/proto/surveyor.adoc2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/ref/proto/surveyor.adoc b/docs/ref/proto/surveyor.adoc
index 4ef51966..8c2fa05b 100644
--- a/docs/ref/proto/surveyor.adoc
+++ b/docs/ref/proto/surveyor.adoc
@@ -68,7 +68,7 @@ When a survey message is received by a forwarding node (see xref:nng_device.adoc
(This peer ID, except for the most significant bit, has meaning only to the forwarding node itself.)
It may help to think of prepending a peer ID as pushing a peer ID onto the front of the stack of headers for the message.
-(It will use the peer IDit popped from the front to determine the next intermediate destination for the response.)
+(It will use the peer ID it popped from the front to determine the next intermediate destination for the response.)
When a response message is created, it is created using the same headers that the survey contained.