FGCOM/dahdi-tools
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

fix typos in some xpp utils

Browse Source 
Signed-off-by: Tzafrir Cohen <tzafrir.cohen@xorcom.com>

git-svn-id: http://svn.astersk.org/svn/dahdi/tools/trunk@10194 17933a7a-c749-41c5-a318-cba88f637d49
This commit is contained in:
Tzafrir Cohen 2011-09-09 10:59:39 +00:00
parent 3482a25b84
commit 67cc13f100
3 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
xpp/dahdi_genconf
View File

@ -111,7 +111,7 @@ __END__
=head1 NAME
dahdi_genconf - Generate configuration for dahdi channels.
dahdi_genconf - Generate configuration for Dahdi channels.
=head1 SYNOPSIS
@ -126,7 +126,7 @@ It uses two information sources:
=item Hardware
The actual dahdi hardware is automatically detected on the host.
The actual Dahdi hardware is automatically detected on the host.
=item /etc/dahdi/genconf_parameters
@ -137,7 +137,7 @@ variable.
=back
The dahdi_genconf script can generate various kinds of configuration files
as specificed by the generator arguments. Each generator is a perl classes
as specified by the generator arguments. Each generator is a perl class
in Dahdi::Config::Gen namespace. The generator names on the command line
are the class names in lowercase.
@ -177,14 +177,14 @@ Currently, chandahdi is affected.
=item *
F<genconf_parameters> parsing is done via C<Dahdi::Config::Params>.
An object representing the parsed data is instanciated by:
An object representing the parsed data is instantiated by:
C<Dahdi::Config::Params-E<gt>new()>.
The C<item()> method of this object contains all the hard coded
defaults of the configuration directives.
=item *
A configuration object is instanciated by C<Dahdi::Config::Gen-E<gt>new($params)>.
A configuration object is instantiated by C<Dahdi::Config::Gen-E<gt>new($params)>.
The mapping of configuration directives into semantic configuration is
done in the constructor.

6
xpp/dahdi_hardware
View File

@ -72,7 +72,7 @@ sub show_disconnected(%) {
# FIXME: For verbose display we also need to see the XPP devices.
# If no spans are registered, this won't happen. A brute-force
# methood for making it happe:
# method for making it happen:
Dahdi::Xpp::xbuses if ($opts{'v'});
my @devices = Dahdi::Hardware->device_list;
@ -139,7 +139,7 @@ dahdi_hardware [-v][-x]
=item -v
Verbose ouput - show spans used by each device etc. Currently only
Verbose output - show spans used by each device etc. Currently only
implemented for the Xorcom Astribank.
=item -x
@ -150,7 +150,7 @@ Show disconnected Astribank unit, if any.
=head1 DESCRIPTION
Show all dahdi hardware devices. Devices are recognized according to
Show all Dahdi hardware devices. Devices are recognized according to
lists of PCI and USB IDs in Dahdi::Hardware::PCI.pm and
Dahdi::Hardware::USB.pm . For PCI it is possible to detect by
sub-vendor and sub-product ID as well.

2
xpp/lsdahdi
View File

@ -48,7 +48,7 @@ __END__
=head1 NAME
lsdahdi - List all dahdi channels with their types and spans.
lsdahdi - List all Dahdi channels with their types and spans.
=head1 SYNOPSIS