Suggested changes by @qlyoung

- Changed hard-linked references to soft-link
- Changed configuration options from code block to ``.. option::`` blocks

Signed-off-by: Jarad Olson <brotherdust+github@gmail.com>
This commit is contained in:
Jarad Olson 2018-05-15 14:04:54 -06:00
parent d5c8283249
commit b2c8e6f847

View File

@ -78,7 +78,9 @@ Download source
Configure Configure
^^^^^^^^^ ^^^^^^^^^
Options below are provided as an example. See `User Guide/Installation <http://frrouting.readthedocs.io/en/latest/installation.html>` for more. Options below are provided as an example.
.. seealso:: *Installation* section of user guide
:: ::
@ -109,19 +111,13 @@ Options below are provided as an example. See `User Guide/Installation <http://f
If optional packages were installed, the associated feature may now be If optional packages were installed, the associated feature may now be
enabled. enabled.
Protobuf .. option:: --enable-protobuf
~~~~~~~~
:: Enable support for protobuf transport
--enable-protobuf .. option:: --enable-zeromq
ZeroMQ Enable support for ZeroMQ transport
~~~~~~
::
--enable-zeromq
Compile Compile
^^^^^^^ ^^^^^^^
@ -141,8 +137,9 @@ are correct. If the files are not already present, FRR will create them.
It's also important to consider _which_ files to create. FRR supports writing It's also important to consider _which_ files to create. FRR supports writing
configuration to a monolithic file, ``/etc/frr/frr.conf``, which is not configuration to a monolithic file, ``/etc/frr/frr.conf``, which is not
recommended, according to the recommended
`user guide <http://frrouting.readthedocs.io/en/latest/vtysh.html>`. .. seealso:: *VTYSH* section of user guide
The presence of ``/etc/frr/frr.conf`` on startup implicitly configures FRR to The presence of ``/etc/frr/frr.conf`` on startup implicitly configures FRR to
ignore daemon-specific configuration files. ignore daemon-specific configuration files.