aboutsummaryrefslogtreecommitdiffstats
path: root/docbook/wsdg_src
diff options
context:
space:
mode:
authorJaap Keuter <jaap.keuter@xs4all.nl>2007-12-10 19:08:14 +0000
committerJaap Keuter <jaap.keuter@xs4all.nl>2007-12-10 19:08:14 +0000
commit3e3453537cbb3b8f051356c0cc69a4348fad1a26 (patch)
treeebfc3e2c5e786648a5b2e4b3c96378a99b1d586b /docbook/wsdg_src
parent1f272d5f5e8fd1a02e1ec30e7d30368b682d3b3d (diff)
Get the paragraph markers right.
svn path=/trunk/; revision=23829
Diffstat (limited to 'docbook/wsdg_src')
-rw-r--r--docbook/wsdg_src/WSDG_chapter_dissection.xml2
1 files changed, 1 insertions, 1 deletions
diff --git a/docbook/wsdg_src/WSDG_chapter_dissection.xml b/docbook/wsdg_src/WSDG_chapter_dissection.xml
index 513e36fe0a..179668b4ca 100644
--- a/docbook/wsdg_src/WSDG_chapter_dissection.xml
+++ b/docbook/wsdg_src/WSDG_chapter_dissection.xml
@@ -27,8 +27,8 @@
There is little difference in having your dissector as either a plugin
or build-in. On the Win32 platform you have limited function access
through what's listed in libwireshark.def, but that is mostly complete.
- <para>
</para>
+ <para>
The big plus is that your rebuild cycle for a plugin is much shorter
than for a build-in one. So starting with a plugin makes initial development
simpler, while deployment of the finished code may well be done as build-in