docs: All instances of "the UHD" have been changed to "UHD". All paths, filenames, variables, etc. have been uniformly emphasized.

1 files changed, 25 insertions, 25 deletions

diff --git a/host/docs/usrp2.rst b/host/docs/usrp2.rst
index 452d4f9af..8a2782982 100644
--- a/host/docs/usrp2.rst
+++ b/host/docs/usrp2.rst
@@ -5,11 +5,11 @@ UHD - USRP2 and N Series Application Notes
 .. contents:: Table of Contents
 
 ------------------------------------------------------------------------
-Load the images onto the SD card (USRP2 only)
+Load the Images onto the SD card (USRP2 only)
 ------------------------------------------------------------------------
 **Warning!**
-Use the usrp2_card_burner.py with caution. If you specify the wrong device node,
-you could overwrite your hard drive. Make sure that --dev= specifies the SD card.
+Use **usrp2_card_burner.py** with caution. If you specify the wrong device node,
+you could overwrite your hard drive. Make sure that **--dev=** specifies the SD card.
 
 **Warning!**
 It is possible to use 3rd party SD cards with the USRP2.
@@ -33,7 +33,7 @@ Use the card burner tool (UNIX)
     sudo ./usrp2_card_burner.py --dev=/dev/sd<XXX> --fpga=<path_to_fpga_image>
     sudo ./usrp2_card_burner.py --dev=/dev/sd<XXX> --fw=<path_to_firmware_image>
 
-Use the *--list* option to get a list of possible raw devices.
+Use the **--list** option to get a list of possible raw devices.
 The list result will filter out disk partitions and devices too large to be the sd card.
 The list option has been implemented on Linux, Mac OS X, and Windows.
 
@@ -45,7 +45,7 @@ Use the card burner tool (Windows)
     <path_to_python.exe> <install-path>/share/uhd/utils/usrp2_card_burner_gui.py
 
 ------------------------------------------------------------------------
-Load the images onto the on-board flash (USRP-N Series only)
+Load the Images onto the On-board Flash (USRP-N Series only)
 ------------------------------------------------------------------------
 The USRP-N Series can be reprogrammed over the network
 to update or change the firmware and FPGA images.
@@ -91,7 +91,7 @@ Continue to hold-down the button until the front-panel LEDs blink and remain sol
 When in safe-mode, the USRP-N device will always have the IP address **192.168.10.2**.
 
 ------------------------------------------------------------------------
-Setup networking
+Setup Networking
 ------------------------------------------------------------------------
 The USRP2 only supports Gigabit Ethernet
 and will not work with a 10/100 Mbps interface.
@@ -102,7 +102,7 @@ to a USRP2 through a Gigabit Ethernet switch.
 Setup the host interface
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 The USRP2 communicates at the IP/UDP layer over the gigabit ethernet.
-The default IP address of the USRP2 is **192.168.10.2**
+The default IP address of the USRP2 is **192.168.10.2**.
 You will need to configure the host's Ethernet interface with a static IP
 address to enable communication.  An address of **192.168.10.1** and a subnet
 mask of **255.255.255.0** is recommended.
@@ -113,15 +113,15 @@ On a Linux system, you can set a static IP address very easily by using the
 
     sudo ifconfig <interface> 192.168.10.1
 
-Note that <interface> is usually something like 'eth0'.  You can discover the
-names of the network interfaces in your computer by running 'ifconfig' without
+Note that **<interface>** is usually something like **eth0**.  You can discover the
+names of the network interfaces in your computer by running **ifconfig** without
 any parameters:
 ::
 
     ifconfig -a
 
 **Note:**
-When using the UHD, if an IP address for the USRP2 is not specified,
+When using UHD, if an IP address for the USRP2 is not specified,
 the software will use UDP broadcast packets to locate the USRP2.
 On some systems, the firewall will block UDP broadcast packets.
 It is recommended that you change or disable your firewall settings.
@@ -168,7 +168,7 @@ Run the following commands:
 
 **Method 2 (Linux Only):**
 This method assumes that you do not know the IP address of your USRP2.
-It uses raw ethernet packets to bypass the IP/UDP layer to communicate with the USRP2.
+It uses raw Ethernet packets to bypass the IP/UDP layer to communicate with the USRP2.
 Run the following commands:
 ::
 
@@ -176,7 +176,7 @@ Run the following commands:
     sudo ./usrp2_recovery.py --ifc=eth0 --new-ip=192.168.10.3
 
 ------------------------------------------------------------------------
-Communication problems
+Communication Problems
 ------------------------------------------------------------------------
 When setting up a development machine for the first time,
 you may have various difficulties communicating with the USRP device.
@@ -187,7 +187,7 @@ RuntimeError: no control response
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 This is a common error that occurs when you have set the subnet of your network
 interface to a different subnet than the network interface of the USRP.  For
-example, if your network interface is set to 192.168.20.1, and the USRP is
+example, if your network interface is set to **192.168.20.1**, and the USRP is
 **192.168.10.2** (note the difference in the third numbers of the IP addresses), you
 will likely see a 'no control response' error message.
 
@@ -206,7 +206,7 @@ If disabling your system's firewall
 or specifying the IP address yields a discovered device,
 then your firewall may be blocking replies to UDP broadcast packets.
 If this is the case, we recommend that you disable the firewall
-or create a rule to allow all incoming packets with UDP source port 49152.
+or create a rule to allow all incoming packets with UDP source port **49152**.
 
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 Ping the device
@@ -226,8 +226,8 @@ Read the serial port to get debug verbose output from the embedded microcontroll
 The microcontroller prints useful information about IP addresses,
 MAC addresses, control packets, fast-path settings, and bootloading.
 Use a standard USB to 3.3v-level serial converter at 230400 baud.
-Connect GND to the converter ground, and connect TXD to the converter receive.
-The RXD pin can be left unconnected as this is only a one-way communication.
+Connect **GND** to the converter ground, and connect **TXD** to the converter receive.
+The **RXD** pin can be left unconnected as this is only a one-way communication.
 
 * **USRP2:** Serial port located on the rear edge
 * **N210:** Serial port located on the left side
@@ -238,7 +238,7 @@ Monitor the host network traffic
 Use Wireshark to monitor packets sent to and received from the device.
 
 ------------------------------------------------------------------------
-Addressing the device
+Addressing the Device
 ------------------------------------------------------------------------
 
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
@@ -248,7 +248,7 @@ In a single-device configuration,
 the USRP device must have a unique IPv4 address on the host computer.
 The USRP can be identified through its IPv4 address, resolvable hostname, or by other means.
 See the application notes on `device identification <./identification.html>`_.
-Use this addressing scheme with the *single_usrp* interface.
+Use this addressing scheme with the **single_usrp** interface.
 
 Example device address string representation for a USRP2 with IPv4 address **192.168.10.2**:
 
@@ -263,7 +263,7 @@ In a multi-device configuration,
 each USRP device must have a unique IPv4 address on the host computer.
 The device address parameter keys must be suffixed with the device index.
 Each parameter key should be of the format <key><index>.
-Use this addressing scheme with the *multi_usrp* interface.
+Use this addressing scheme with the **multi_usrp** interface.
 
 * The order in which devices are indexed corresponds to the indexing of the transmit and receive channels.
 * The key indexing provides the same granularity of device identification as in the single device case.
@@ -316,7 +316,7 @@ the following clock configuration must be set on the slave device:
     usrp->set_clock_config(clock_config, slave_index);
 
 ------------------------------------------------------------------------
-Hardware setup notes
+Hardware Setup Notes
 ------------------------------------------------------------------------
 
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
@@ -353,7 +353,7 @@ Using a PPS signal for timestamp synchronization requires a square wave signal w
 
 Test the PPS input with the following app:
 
-* <args> are device address arguments (optional if only one USRP is on your machine)
+* **<args>** are device address arguments (optional if only one USRP is on your machine)
 
 ::
 
@@ -386,13 +386,13 @@ Multiple RX channels
 There are two complete DDC chains in the FPGA.
 In the single channel case, only one chain is ever used.
 To receive from both channels,
-the user must set the RX subdevice specification.
+the user must set the **RX** subdevice specification.
 This hardware has only one daughterboard slot,
-which has been aptly named slot "A".
+which has been aptly named slot **A**.
 
 In the following example, a TVRX2 is installed.
-Channel 0 is sourced from subdevice RX1,
-channel 1 is sourced from subdevice RX2:
+Channel 0 is sourced from subdevice **RX1**,
+and channel 1 is sourced from subdevice **RX2**:
 ::
 
     usrp->set_rx_subdev_spec("A:RX1 A:RX2");