Documentation: Adapt format suggested by docstrfmt

docs/guide/example_binary.rst

@@ -6,9 +6,9 @@
 Example Create-Binary Execution
 ===============================
 
-We'll compile this SystemVerilog example into a Verilated simulation binary.  For
-an example that discusses the next level of detail see :ref:`Example C++
-Execution`.
+We'll compile this SystemVerilog example into a Verilated simulation
+binary. For an example that discusses the next level of detail see
+:ref:`Example C++ Execution`.
 
 .. include:: example_common_install.rst
 
@@ -16,20 +16,20 @@ Now, let's create an example Verilog file:
 
 .. code-block:: bash
 
-     mkdir test_our
-     cd test_our
+   mkdir test_our
+   cd test_our
 
-     cat >our.v <<'EOF'
-       module our;
-          initial begin $display("Hello World"); $finish; end
-       endmodule
-     EOF
+   cat >our.v <<'EOF'
+     module our;
+        initial begin $display("Hello World"); $finish; end
+     endmodule
+   EOF
 
 Now we run Verilator on our little example.
 
 .. code-block:: bash
 
-     verilator --binary -j 0 -Wall our.v
+   verilator --binary -j 0 -Wall our.v
 
 Breaking this command down:
 
@@ -48,16 +48,16 @@ And now we run it:
 
 .. code-block:: bash
 
-     obj_dir/Vour
+   obj_dir/Vour
 
 And we get as output:
 
 .. code-block:: bash
 
-     Hello World
-     - our.v:2: Verilog $finish
+   Hello World
+   - our.v:2: Verilog $finish
 
 You're better off using a Makefile to run the steps for you, so when your
-source changes, it will automatically run all of the appropriate steps.  To
-aid this, Verilator can create a makefile dependency file.  For examples
+source changes, it will automatically run all of the appropriate steps. To
+aid this, Verilator can create a makefile dependency file. For examples
 that do this, see the :file:`examples` directory in the distribution.