aboutsummaryrefslogtreecommitdiffstats
path: root/docbook/wsdg_src/WSDG_chapter_dissection.xml
diff options
context:
space:
mode:
Diffstat (limited to 'docbook/wsdg_src/WSDG_chapter_dissection.xml')
-rw-r--r--docbook/wsdg_src/WSDG_chapter_dissection.xml6
1 files changed, 3 insertions, 3 deletions
diff --git a/docbook/wsdg_src/WSDG_chapter_dissection.xml b/docbook/wsdg_src/WSDG_chapter_dissection.xml
index ec9909692b..eaf8b0c194 100644
--- a/docbook/wsdg_src/WSDG_chapter_dissection.xml
+++ b/docbook/wsdg_src/WSDG_chapter_dissection.xml
@@ -25,13 +25,13 @@
</para>
<para>
There is little difference in having your dissector as either a plugin
- or build-in. On the Win32 platform you have limited function access
+ or built-in. On the Win32 platform you have limited function access
through what's listed in libwireshark.def, but that is mostly complete.
</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
+ than for a built-in one. So starting with a plugin makes initial development
+ simpler, while deployment of the finished code may well be done as built-in
dissector.
</para>
<note><title>See also README.developer</title>