Fix space issues

This commit is contained in:
Cary R 2023-06-10 19:43:26 -07:00
parent bff91566ab
commit 6307057e8d
7 changed files with 8 additions and 8 deletions

View File

@ -8,10 +8,10 @@ source code itself, so that you can find the global parts where you
can look for even better detail.
The documentation for getting, building and installing Icarus Verilog
is kept and maintained at :doc:`Getting Started as a Contributer <../getting_started>`
is kept and maintained at :doc:`Getting Started as a Contributer <../getting_started>`
See the Installation Guide for getting the current source from the git
repository (and how to use the git repository) and see the Developer Guide
repository (and how to use the git repository) and see the Developer Guide
for instructions on participating in the Icarus Verilog development process.
That information will not be repeated here.

View File

@ -21,7 +21,7 @@ Procedural assignments have to be given one at a time, to be
always @ (posedge Clk) Y = newY;
always @ (posedge Clk) Z = newZ;
rather than
::

View File

@ -32,7 +32,7 @@ include implementations of private functions used to support VHDL.
Compiling A VPI Module
----------------------
See the documentation under: :doc:`Using VPI <../../../usage/vpi>`
See the documentation under: :doc:`Using VPI <../../../usage/vpi>`
Tracing VPI Use
---------------

View File

@ -10,4 +10,4 @@ VVP - Verilog Virtual Processor
vpi
vthread
debug

View File

@ -531,7 +531,7 @@ the description when it is executed. The output is sent to stderr and
the format of the output is:
<file>:<line>: <description>
<file> is the unsigned numeric file index.
<line> is the unsigned line number.
<description> is a string, if string is 0 then the following default

View File

@ -28,7 +28,7 @@ With this example code:
out <= !out;
end
end
assign blink = out;
endmodule

View File

@ -60,4 +60,4 @@ Next are some directives. The first one, `:ivl_version` specifies which version
Opcodes
-------
The various available opcodes can be seen in :doc:`Opcodes <../developer/guide/vvp/opcodes>`
The various available opcodes can be seen in :doc:`Opcodes <../developer/guide/vvp/opcodes>`