Deployed 7a4f716 to 1.0 with MkDocs 1.3.0 and mike 1.1.2

Author: ArduinoBot

1.0/CONTRIBUTING/index.html

@@ -1860,7 +1860,7 @@ <h3 id="prerequisites">Prerequisites<a class="headerlink" href="#prerequisites"
 <li>download and install the <a href="https://github.com/protocolbuffers/protobuf/releases">protoc</a> compiler (use the version required to match the generated code, please note that
   the latest releases does not follow semantic versioning anymore so, for example, the version 5.26.1 must be searched
   as 26.1 dropping the major number)</li>
-<li>install <code>protoc-gen-go</code> using: <code>go install google.golang.org/protobuf/cmd/[email protected].1</code> (use the version
+<li>install <code>protoc-gen-go</code> using: <code>go install google.golang.org/protobuf/cmd/[email protected].2</code> (use the version
   required to match the generated code)</li>
 <li>install <code>protoc-gen-go-grpc</code> using: <code>go install google.golang.org/grpc/cmd/[email protected]</code> (use the version
   required to match the generated code)</li>

1.0/commands/arduino-cli_monitor/index.html

@@ -1457,6 +1457,8 @@ <h3 id="synopsis">Synopsis<a class="headerlink" href="#synopsis" title="Permanen
 </code></pre></div>
 <h3 id="examples">Examples<a class="headerlink" href="#examples" title="Permanent link">&para;</a></h3>
 <div class="highlight"><pre><span></span><code>  arduino-cli monitor -p /dev/ttyACM0
+  arduino-cli monitor -p /dev/ttyACM0 -b arduino:avr:uno
+  arduino-cli monitor -p /dev/ttyACM0 --config 115200
   arduino-cli monitor -p /dev/ttyACM0 --describe
 </code></pre></div>
 <h3 id="options">Options<a class="headerlink" href="#options" title="Permanent link">&para;</a></h3>

1.0/platform-specification/index.html

@@ -2821,14 +2821,14 @@ <h2 id="boardstxt">boards.txt<a class="headerlink" href="#boardstxt" title="Perm
 <p>If the platform supports pluggable discovery it may also declare a set of <code>upload_port.*</code> properties, these properties
 will be used to identify a board by the discovery process when plugged in.</p>
 <p>For example we could declare a series of <code>upload_port.vid</code> and <code>upload_port.pid</code> properties for the Uno like so:</p>
-<div class="highlight"><pre><span></span><code>uno.upload_port.vid.0=0x2341
-uno.upload_port.pid.0=0x0043
-uno.upload_port.vid.1=0x2341
-uno.upload_port.pid.1=0x0001
-uno.upload_port.vid.2=0x2A03
-uno.upload_port.pid.2=0x0043
-uno.upload_port.vid.3=0x2341
-uno.upload_port.pid.3=0x0243
+<div class="highlight"><pre><span></span><code>uno.upload_port.0.vid=0x2341
+uno.upload_port.0.pid=0x0043
+uno.upload_port.1.vid=0x2341
+uno.upload_port.1.pid=0x0001
+uno.upload_port.2.vid=0x2A03
+uno.upload_port.2.pid=0x0043
+uno.upload_port.3.vid=0x2341
+uno.upload_port.3.pid=0x0243
 </code></pre></div>
 <p>In this case we're using the board's USB VID/PID pair to identify it but <code>upload_port.*</code> properties can be anything that
 can help identify a certain board. For more detailed information see the