From 9c13d98ce919a55252b45c7dd3e9edbd9da56e7e Mon Sep 17 00:00:00 2001
From: Tom Fifield <tom@openstack.org>
Date: Thu, 23 Jan 2014 10:32:55 -0500
Subject: [PATCH] Address editor comments for Network Troubleshooting

* add introductory sentence for tcpdump

Change-Id: I7945a39745933d70996ca56653aba17e98b292ba
---
 doc/openstack-ops/ch_ops_network_troubleshooting.xml | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/doc/openstack-ops/ch_ops_network_troubleshooting.xml b/doc/openstack-ops/ch_ops_network_troubleshooting.xml
index 89782c5b..6b148fe4 100644
--- a/doc/openstack-ops/ch_ops_network_troubleshooting.xml
+++ b/doc/openstack-ops/ch_ops_network_troubleshooting.xml
@@ -128,7 +128,8 @@
     <section xml:id="tcpdump">
         <title>tcpdump</title>
         <para>One great, although very in-depth, way of
-            troubleshooting network issues is to use tcpdump. It's
+            troubleshooting network issues is to use tcpdump. The tcpdump
+            tool captures network packets for analysis. It's
             recommended to use tcpdump at several points along the
             network path to correlate where a problem might be. If you
             prefer working with a GUI, either live or by using a