From 12685e71f3e5e0330ca2c4563fd4a887b2176e7e Mon Sep 17 00:00:00 2001 From: Saivann Date: Thu, 20 Nov 2014 19:48:19 -0500 Subject: [PATCH] Fix a few typos --- _includes/ref_p2p_networking.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/_includes/ref_p2p_networking.md b/_includes/ref_p2p_networking.md index 48c182fa..a8407d9f 100644 --- a/_includes/ref_p2p_networking.md +++ b/_includes/ref_p2p_networking.md @@ -679,19 +679,19 @@ introduced in protocol version 311. | 4 | version | int32_t | Alert format version. Version 1 from protocol version 311 through at least protocol version 70002. | 8 | relayUntil | int64_t | The time beyond which nodes should stop relaying this alert. Unix epoch time format. | 8 | expiration | int64_t | The time beyond which this alert is no longer in effect and should be ignored. Unix epoch time format. -| 4 | ID | int32_t | A unique ID number for this alert -| 4 | cancel | int32_t | All alerts with an ID number less than or equal to this number should be canceled: deleted and not accepted in the future +| 4 | ID | int32_t | A unique ID number for this alert. +| 4 | cancel | int32_t | All alerts with an ID number less than or equal to this number should be canceled: deleted and not accepted in the future. | *Varies* | setCancel count | compactSize uint | The number of IDs in the following setCancel field. May be zero. | *Varies* | setCancel | int32_t | Alert IDs which should be canceled. Each alert ID is a separate int32_t number. | 4 | minVer | int32_t | This alert only applies to protocol versions greater than or equal to this version. Nodes running other protocol versions should still relay it. | 4 | maxVer | int32_t | This alert only applies to protocol versions less than or equal to this version. Nodes running other protocol versions should still relay it. | *Varies* | user\_agent count | compactSize uint | The number of user agent strings in the following setUser\_agent field. May be zero. | *Varies* | setUser\_agent | compactSize uint + string | If this field is empty, it has no effect on the alert. If there is at least one entry is this field, this alert only applies to programs with a user agent that exactly matches one of the strings in this field. Each entry in this field is a compactSize uint followed by a string---the uint indicates how many bytes are in the following string. This field was originally called setSubVer; since BIP14, it applies to user agent strings as defined in the `version` message. -| 4 | priority | int32_t | Relative priority compared to other alerts +| 4 | priority | int32_t | Relative priority compared to other alerts. | *Varies* | comment bytes | compactSize uint | The number of bytes in the following comment field. May be zero. -| *Varies* | comment | string | A comment on the alert that is not displayed +| *Varies* | comment | string | A comment on the alert that is not displayed. | *Varies* | statusBar bytes | compactSize uint | The number of bytes in the following statusBar field. May be zero. -| *Varies* | statusBar | string | The alert message that is displayed to the user +| *Varies* | statusBar | string | The alert message that is displayed to the user. | *Varies* | reserved bytes | compactSize uint | The number of bytes in the following reserved field. May be zero. | *Varies* | reserved | string | Reserved for future use. Originally called RPC Error. @@ -766,7 +766,7 @@ privacy should recalculate the bloom filter themselves and send a new | *Varies* | object bytes | compactSize uint | The number of bytes in the following object field. | *Varies* | object | uint8_t[] | The object to add to the current filter. Maximum of 520 bytes, which is the maximum size of an object which can be pushed onto the stack in a pubkey or signature script. Objects must be sent in the byte order they would use when appearing in a raw transaction; for example, hashes should be sent in internal byte order. -The annotated hexdump below shows an `filteradd` message adding a TXID. +The annotated hexdump below shows a `filteradd` message adding a TXID. (The message header has been omitted.) This TXID appears in the same block used for the example hexdump in the `merkleblock` message; if that `merkleblock` message is re-sent after sending this `filteradd` message,