docs: Fix typos (#15421)
This commit is contained in:
parent
18292475fd
commit
b516ead921
|
|
@ -537,7 +537,7 @@ ifSpecific OBJECT-TYPE
|
|||
object refers to a document defining objects
|
||||
specific to ethernet. If this information is not
|
||||
present, its value should be set to the OBJECT
|
||||
IDENTIFIER { 0 0 }, which is a syntatically valid
|
||||
IDENTIFIER { 0 0 }, which is a syntactically valid
|
||||
object identifier, and any conformant
|
||||
implementation of ASN.1 and BER must be able to
|
||||
generate and recognize this value."
|
||||
|
|
@ -1249,7 +1249,7 @@ ipRouteInfo OBJECT-TYPE
|
|||
specified in the route's ipRouteProto value. If
|
||||
this information is not present, its value should
|
||||
be set to the OBJECT IDENTIFIER { 0 0 }, which is
|
||||
a syntatically valid object identifier, and any
|
||||
a syntactically valid object identifier, and any
|
||||
conformant implementation of ASN.1 and BER must be
|
||||
able to generate and recognize this value."
|
||||
::= { ipRouteEntry 13 }
|
||||
|
|
|
|||
|
|
@ -42,7 +42,7 @@ execd plugins:
|
|||
an input gathering plugin, you may see data right away, or you may have to hit enter
|
||||
first, or wait for your poll duration to elapse, but the metrics will be written to
|
||||
STDOUT. Ctrl-C to end your test.
|
||||
If you're testig a processor or output manually, you can still do this but you
|
||||
If you're testing a processor or output manually, you can still do this but you
|
||||
will need to feed valid metrics in on STDIN to verify that it is doing what you
|
||||
want. This can be a very valuable debugging technique before hooking it up to
|
||||
Telegraf.
|
||||
|
|
|
|||
Loading…
Reference in New Issue