diff --git a/nodes/core/hardware/36-rpi-gpio.html b/nodes/core/hardware/36-rpi-gpio.html index 8a832578d..533f26a6a 100644 --- a/nodes/core/hardware/36-rpi-gpio.html +++ b/nodes/core/hardware/36-rpi-gpio.html @@ -179,7 +179,7 @@
payload number
the payload will be a 1 or a 0.
topic string
-
the topic will be set to `pi/{the pin number}`.
+
the topic will be set to pi/{the pin number}.

Details

You may also enable the input pullup resistor or the pulldown resistor.

diff --git a/nodes/core/io/21-httpin.html b/nodes/core/io/21-httpin.html index f3b7e16d9..739897e8f 100644 --- a/nodes/core/io/21-httpin.html +++ b/nodes/core/io/21-httpin.html @@ -75,7 +75,7 @@

The node will listen on the configured path for requests of a particular type. The path can be fully specified, such as /user, or include named parameters that accept any value, such as /user/:name. - When named parameters are used, their actual value in a request can be accessed under `msg.req.params`.

+ When named parameters are used, their actual value in a request can be accessed under msg.req.params.

For requests that include a body, such as a POST or PUT, the contents of the request is made available as msg.payload.

If the content type of the request can be determined, the body will be parsed to diff --git a/nodes/core/io/21-httprequest.html b/nodes/core/io/21-httprequest.html index 5c57d47e9..0d7119cb9 100644 --- a/nodes/core/io/21-httprequest.html +++ b/nodes/core/io/21-httprequest.html @@ -117,7 +117,7 @@ the response headers. The next node will then use those headers for its request - this is not usually the right thing to do. If msg.headers property is left unchanged between nodes, it will be ignored by the second node. To set custom headers, msg.headers - should first be deleted or reset to an empty object: `{}`. + should first be deleted or reset to an empty object: {}.

Cookie handling

The cookies property passed to the node must be an object of name/value pairs. The value can be either a string to set the value of the cookie or it can be an diff --git a/nodes/core/logic/10-switch.html b/nodes/core/logic/10-switch.html index 9205f72b0..219654829 100644 --- a/nodes/core/logic/10-switch.html +++ b/nodes/core/logic/10-switch.html @@ -65,7 +65,7 @@ that are part of a sequence.

The recreate message sequences option can be enabled to generate new message sequences for each rule that matches. In this mode, the node will buffer the entire incoming - sequence before sending the new sequences on. The runtime setting `nodeMessageBufferMaxLength` + sequence before sending the new sequences on. The runtime setting nodeMessageBufferMaxLength can be used to limit how many messages nodes will buffer.

diff --git a/nodes/core/logic/17-split.html b/nodes/core/logic/17-split.html index 49480ba53..603443c21 100644 --- a/nodes/core/logic/17-split.html +++ b/nodes/core/logic/17-split.html @@ -337,7 +337,7 @@

Storing messages

This node will buffer messages internally in order to work across sequences. The - runtime setting `nodeMessageBufferMaxLength` can be used to limit how many messages nodes + runtime setting nodeMessageBufferMaxLength can be used to limit how many messages nodes will buffer.

diff --git a/nodes/core/logic/19-batch.html b/nodes/core/logic/19-batch.html index 6d522d5ec..ef4065d33 100644 --- a/nodes/core/logic/19-batch.html +++ b/nodes/core/logic/19-batch.html @@ -90,7 +90,7 @@

Storing messages

This node will buffer messages internally in order to work across sequences. The - runtime setting `nodeMessageBufferMaxLength` can be used to limit how many messages nodes + runtime setting nodeMessageBufferMaxLength can be used to limit how many messages nodes will buffer.