various updates to man pages

git-svn-id: http://svn.asterisk.org/svn/dahdi/tools/trunk@4732 a0bf4364-ded3-4de4-8d8a-66a801d63aff

8 files changed, 23 insertions, 23 deletions

diff --git a/doc/dahdi_cfg.8 b/doc/dahdi_cfg.8
index 18e8e58..34bd70d 100644
--- a/doc/dahdi_cfg.8
+++ b/doc/dahdi_cfg.8
@@ -1,7 +1,7 @@
 .TH "DAHDI_CFG" "8" "16 Jun 2008" "" ""
 
 .SH NAME
-dahdi_cfg \- configures dahdi kernel modules from /etc/dahdi/system.conf
+dahdi_cfg \- configures DAHDI kernel modules from /etc/dahdi/system.conf
 .SH SYNOPSIS
 
 .B dahdi_cfg [-c \fICFG_FILE\fB] [-s] [-f] [-t] [-v [-v ... ] ]
@@ -10,10 +10,10 @@ dahdi_cfg \- configures dahdi kernel modules from /etc/dahdi/system.conf
 
 .SH DESCRIPTION
 .B dahdi_cfg 
-configures dahdi interface cards from a config file.
+configures DAHDI interface cards from a config file.
 
-You  generally  need to run it with a valid configurations
-in order for zaptel modules to work properly.
+You generally  need to run it with a valid configurations
+in order for DAHDI modules to work properly.
 
 It must be run to configure every DAHDI span. Normally it is run from
 the DAHDI init script.
diff --git a/doc/dahdi_diag.8 b/doc/dahdi_diag.8
index eabd6c1..59fd6c5 100644
--- a/doc/dahdi_diag.8
+++ b/doc/dahdi_diag.8
@@ -1,13 +1,13 @@
 .TH dahdi_diag 8 "2008-01-07" 
 .SH NAME 
-dahdi_diag \(em Dump Zaptel channel parameters
+dahdi_diag \(em Dump DAHDI channel parameters
 .SH SYNOPSIS 
 .B dahdi_diag 
 .I channel
 
 .SH DESCRIPTION 
 .B dahdi_diag
-asks the kernel to dump parameters for Zaptel channel no.
+asks the kernel to dump parameters for DAHDI channel no.
 .I channel
 to the kernel logs. You will be able to see them using, e.g. dmesg(1).
 
@@ -15,15 +15,15 @@ to the kernel logs. You will be able to see them using, e.g. dmesg(1).
 .SH OPTIONS
 .I channel
 .RS
-The number of the Zaptel channel whose parammeters should be dumped.
-May be any Zaptel channel (even if it is open).
+The number of the DAHDI channel whose parammeters should be dumped.
+May be any DAHDI channel (even if it is open).
 .RE
 
 .SH EXAMPLE
 
   # /tmp/dahdi_diag 5
   # dmesg | tail -n 15
-  Dump of Zaptel Channel 5 (XPP_BRI_TE/00/01/1,5,2):
+  Dump of DAHDI Channel 5 (XPP_BRI_TE/00/01/1,5,2):
 
   flags: 501 hex, writechunk: c5190948, readchunk: c5190954
   rxgain: ccad2e80, txgain: ccad2e80, gainalloc: 0
diff --git a/doc/dahdi_monitor.8 b/doc/dahdi_monitor.8
index ed989be..ce9e464 100644
--- a/doc/dahdi_monitor.8
+++ b/doc/dahdi_monitor.8
@@ -1,14 +1,14 @@
 .TH "DAHDI_MONITOR" "8" "16 June 2008" "" ""
 
 .SH NAME
-dahdi_monitor \- checks the rx/tx levels of the dahdi inteface cards.
+dahdi_monitor \- checks the rx/tx levels of DAHDI channels
 .SH SYNOPSIS
 
 .B dahdi_monitor \fIchannel number\fB [-v] [-f \fIFILE\fB]
 
 .SH DESCRIPTION
 
-dahdi_monitor monitors a zaptel channel. It gives you a visual
+dahdi_monitor monitors a DAHDI channel. It gives you a visual
 representation of the sound strengths and makes it easy to see if
 the received or transmitted signals are too high or out of
 balance
diff --git a/doc/dahdi_scan.8 b/doc/dahdi_scan.8
index c351db9..76b61b2 100644
--- a/doc/dahdi_scan.8
+++ b/doc/dahdi_scan.8
@@ -1,13 +1,13 @@
 .TH dahdi_scan 8 "2008-03-18" 
 .SH NAME 
-dahdi_scan \(em Print Configuration of Zaptel Spans
+dahdi_scan \(em Print Configuration of DAHDI Spans
 .SH SYNOPSIS 
 .B dahdi_scan
 .I [spans]
 
 .SH DESCRIPTION 
 .B dahdi_scan
-prints information about dahdi spans in the system. For analog spans it
+prints information about DAHDI spans in the system. For analog spans it
 also provides a list of channels.
 
 By default it prints information about all the spans in the system.
@@ -87,7 +87,7 @@ dahdi_cfg(8), asterisk(8).
 The program still does not do everything described in the man page.
 
 It also assumes that spans don't skip channel numbers, and that their 
-channels numbers are "running". This is anyway almost always the case. 
+channel numbers are "running". This is anyway almost always the case. 
 And always the case in a normal boot process.
 
 .SH AUTHOR 
diff --git a/doc/dahdi_test.8 b/doc/dahdi_test.8
index c61f0f6..21cda80 100644
--- a/doc/dahdi_test.8
+++ b/doc/dahdi_test.8
@@ -1,6 +1,6 @@
 .TH dahdi_test 8 "2005-06-25" 
 .SH "NAME" 
-dahdi_test \(em Test if the dahdi timer provides timely response
+dahdi_test \(em Test if the DAHDI timer provides timely response
 .SH "SYNOPSIS" 
 .B dahdi_test 
 .I [ -v ]
@@ -10,7 +10,7 @@ dahdi_test \(em Test if the dahdi timer provides timely response
 dahdi_test runs a timing test in a loop and prints the result of each loop.
 The test is as follows:
 
-It reads 8192 bytes from the dahdi timer device (\fI/dev/dahdi/pseudo\fR). 
+It reads 8192 bytes from the DAHDI timer device (\fI/dev/dahdi/pseudo\fR). 
 This should take exactly 8000 ms . It uses calls to
 .I gettimeofday(2) 
 before and after that read to check that indeed exactly 8000ms have passed.
@@ -37,7 +37,7 @@ times instead of running forever.
 .B /dev/dahdi/pseudo
 .RS
 .RE
-The device file used to access the dahdi timer.
+The device file used to access the DAHDI timer.
 
 .SH SEE ALSO 
 dahdi_tool(8), dahdi_cfg(8), asterisk(8). gettimeofday(2)
diff --git a/doc/dahdi_tool.8 b/doc/dahdi_tool.8
index 7cad136..2777366 100644
--- a/doc/dahdi_tool.8
+++ b/doc/dahdi_tool.8
@@ -1,7 +1,7 @@
 .TH "DAHDI_TOOL" "8" "16 June 2008" "" ""
 
 .SH NAME
-dahdi_tool \- Zaptel Tool shows status of Digium's interface cards.
+dahdi_tool \- Shows status of DAHDI interfaces
 .SH SYNOPSIS
 
 .B dahdi_tool
diff --git a/doc/fxotune.8 b/doc/fxotune.8
index 7f0236f..65fcb61 100644
--- a/doc/fxotune.8
+++ b/doc/fxotune.8
@@ -24,7 +24,7 @@ It writes settings to a configuration file (/etc/fxotune.conf)
 from which it can be loaded (e.g: at startup) using -s .
 
 .I Dump mode (-d):
-Runs detection on a single Zaptel channel, and just dumps waveforms to
+Runs detection on a single DAHDI channel, and just dumps waveforms to
 .B fxotune_dump.vals
 is generated in the current directory.
 
@@ -36,7 +36,7 @@ it and that are connected. Note that the tunning is affected by e.g.
 the physical parameters of the connection, and thus if it has been 
 radically changed, you may need to re-run fxotune.
 
-FXOTune only works for the Digium TDM400P/800P/2400P cards and
+This program only works for the Digium TDM400P/800P/2400P cards and
 compatible and the Xorcom Astribank devices. Other cards (notably X100P
 cards and clones) do not have the hardware to support such tuning.
 
@@ -117,7 +117,7 @@ and dialing the dial-string.
 .I detect-type
 .RS
 This option allows using the older detection method used by fxotune of
-zaptel 1.2. use 
+Zaptel 1.2. use 
 .B -t 1
 for that older method. whereas
 .B -t 2
@@ -173,7 +173,7 @@ destroy channel NNN): other channels will be used by Asterisk, and hence
 skipped. This can be useful if you have many FXO ports that are not connected.
 
 .B fxotune
-writes immedietly to 
+writes immediately to 
 .B /etc/fxotune.conf
 so if you stop it half-way, you may get a half-configured system. If you
 have already tuned your FXO channels and wish to test-run fxotune again, 
diff --git a/doc/fxstest.8 b/doc/fxstest.8
index 6caa855..159480f 100644
--- a/doc/fxstest.8
+++ b/doc/fxstest.8
@@ -1,7 +1,7 @@
 .TH "FXSTEST" "8" "9 June 2007" "asterisk" "System Manager's Manuals: Asterisk"
 
 .SH NAME
-fxstest \- Simple tests for Zaptel FXS adapters
+fxstest \- Simple tests for DAHDI FXS adapters
 .SH SYNOPSIS
 
 .B fxstest /dev/dahdi/\fIN comand\fR