TT#22411 Fix spelling mistakes/typos

s/Syncronizes/Synchronizes/
s/Wheras/Whereas/
s/configuation/configuration/
s/exisiting/existing/
s/explicitely/explicitly/
s/files files/files/
s/has has/has/
s/initialise initialise/initialise/
s/mulitple/multiple/
s/ouput/output/
s/propogates/propagates/
s/successfull/successful/
s/syncronizes/synchronizes/
s/the the/the/
s/uncommited/uncommitted/

Change-Id: Id13ec889c5de620b675e357d99066688cfc97617

docs/ngcpcfg.txt

@@ -109,7 +109,7 @@ file is usually provided by a Debian package.
 * _/etc/ngcp-config/templates/etc/foobar/baz.tt2.$HA_NODE_: node specific
 template file. $HA_NODE is determined using the content of /etc/ngcp_ha_node
 (usually being _sp1_ for the first node and _sp2_ for the second node on the
-Sipwise Next Generation Platform). Wheras _*customtt.tt2_ files are used on all
+Sipwise Next Generation Platform). Whereas _*customtt.tt2_ files are used on all
 nodes in a High Availability setup the _*.tt2.$HA_NODE*_ file is specific for
 the single node only. A common usage case is master vs. slave configuration of a
 service. Configuration file is usually provided by a Debian package.
@@ -330,7 +330,7 @@ _/etc/ngcp-config_. You can specify options for the underlying 'git diff'
 command, e.g. 'ngcpcfg diff HEAD^' will show all changes that have been recorded
 with the last _commit_ operation (see manpage git-rev-parse(1) for details how
 to specify revisions). If the tool doesn't report anything it means that there
-are neither any uncommited changes nor any new or removed files (files which are
+are neither any uncommitted changes nor any new or removed files (files which are
 not yet (un)registered to the repository).
 
   **encrypt**::
@@ -378,7 +378,7 @@ to also skip the _apply_ operation).  If the '--shared-only' option is set then
 the any pending commits will be pushed only to the shared repository only, any
 foreign hosts will be skipped then.  If hostname(s) or IP address(es) is given
 as argument then the changes will be pushed to the shared repository and to the
-given hosts only. If no host has has been specified then the hosts specified in
+given hosts only. If no host has been specified then the hosts specified in
 _/etc/ngcp-config/systems.cfg_ are used.
 Note: This option is available in the High Availability setup only.
 
@@ -468,7 +468,7 @@ Does ngcpcfg also track file permissions?
 -----------------------------------------
 
 When using ngcpcfg in a HA setup (PRO/CARRIER only) you want to ensure that
-changing file permissions inside the ngcpcfg repository on one node propogates
+changing file permissions inside the ngcpcfg repository on one node propagates
 to the other node(s) as well.  ngcpcfg is using git underneath, though git
 itself doesn't track file permissions (except for the execution bit).
 

functions/main

@@ -116,7 +116,7 @@ get_branch_status() {
   fi
 }
 
-## important variables we depend on to operate successfully {{{
+## important variables we depend on to operate successfuly {{{
 # support test suite which requires system independent configuration
 if [ -r "${NGCPCFG:-}" ] ; then
   log_debug "sourcing configuration file ${NGCPCFG:-}"
@@ -334,7 +334,7 @@ record_commit_id() {
   log_debug "mkdir -p ${STATE_FILES_DIR}"
   mkdir -p "${STATE_FILES_DIR}"
 
-  # if there are uncommited changes then record it as such
+  # if there are uncommitted changes then record it as such
   if git status --porcelain | grep -q . ; then
     echo "dirty" > "${STATE_FILES_DIR}/build"
   else

helper/sort-yml

@@ -8,7 +8,7 @@ use warnings;
 use YAML::XS;
 
 my $inputfile  = shift or die 'You did not specify an input file name';
-my $outputfile = shift or die 'You did not specify an ouput file name';
+my $outputfile = shift or die 'You did not specify an output file name';
 
 my $yaml = YAML::XS::LoadFile($inputfile);
 

sbin/ngcp-network

@@ -728,7 +728,7 @@ NOTE: If multiple B<--set-interface> options are specified in one command line
 (e.g. 'B<--set-interface=lo --set-interface=eth0 --set-interface=eth1>') then
 options like B<--hwaddr> cannot be sanely combined with different settings on
 multiple interfaces. Instead invoke ngcp-network with the B<--set-interface>
-option mulitple times.
+option multiple times.
 
 =item B<--shared-ip>=I<IP>
 

sbin/ngcp-network-validator

@@ -219,7 +219,7 @@ B<ngcp-network-validator> [I<option>...]
 =head1 DESCRIPTION
 
 B<This program> generates a schema at run-time to accurately validate this
-system specific network.yml, with the information gathered from the the
+system specific network.yml, with the information gathered from the
 same file.
 
 =head1 OPTIONS

sbin/ngcp-sync-constants

@@ -1,6 +1,6 @@
 #!/usr/bin/perl
 #----------------------------------------------------------------------
-# Syncronizes passwords from constants.yml with MySQL
+# Synchronizes passwords from constants.yml with MySQL
 #----------------------------------------------------------------------
 use strict;
 use warnings;
@@ -32,7 +32,7 @@ my $mysql_root      = 0;
 sub Usage {
     print <<USAGE;
 ==
-    Syncronizes passwords from constants.yml with MySQL
+    Synchronizes passwords from constants.yml with MySQL
 ==
 $PROGRAM_NAME [options]
 Options:
@@ -338,7 +338,7 @@ __END__
 
 =head1 NAME
 
-ngcp-sync-constants - syncronizes passwords from constants.yml with MySQL
+ngcp-sync-constants - synchronizes passwords from constants.yml with MySQL
 
 =head1 SYNOPSIS
 
@@ -346,7 +346,7 @@ B<ngcp-sync-constants> [I<options>...]
 
 =head1 DESCRIPTION
 
-B<This program> reads constants.yml file, parses it and syncronizes all
+B<This program> reads constants.yml file, parses it and synchronizes all
 required passwords with MySQL.
 
 =head1 OPTIONS

scripts/build

@@ -29,7 +29,7 @@ fi
 
 # Sanity check the YAML and schema files.
 # NOTE: we can't blindly pass "$@" to the check script,
-#       so explicitely check and add option as needed
+#       so explicitly check and add option as needed
 if "$CHECK_BRANCH" ; then
   "${SCRIPTS}"/check
 else
@@ -107,7 +107,7 @@ else
   fi
 
   if $trigger_rebuild ; then
-    log_info "Main configuation file(s) has been changed, running full rebuild."
+    log_info "Main configuration file(s) has been changed, running full rebuild."
     log_debug "Executing: build_config_files $*"
     build_config_files "$@"
   fi

scripts/check

@@ -113,7 +113,7 @@ validate_config() {
   done
 
   if [ "$rc" = "0" ] ; then
-    log_info "yml configs were validated successfully"
+    log_info "yml configs were validated successfuly"
   else
     if [ -n "${NO_VALIDATE:-}" ] ; then
       log_info "DANGEROUS ZONE: invalid configs detected, continue anyway due to option '--no-validate'"
@@ -183,7 +183,7 @@ check_configs_conflicts
 
 check_shared_storage || exit $?
 
-log_info "configs were checked successfully"
+log_info "configs were checked successfuly"
 exit 0
 
 ## END OF FILE #################################################################

scripts/clean

@@ -361,7 +361,7 @@ if ${branches} ; then
 fi
 
 if [ "${RC}" = "0" ] ; then
-  log_info "All operations were finished successfully. Good to be clean!"
+  log_info "All operations were finished successfuly. Good to be clean!"
 else
   log_error "Some operations finished with an error, see details above."
 fi

scripts/decrypt

@@ -9,7 +9,7 @@ set -o pipefail
 # helper functions {{{
 # sadly we can't source ${FUNCTIONS}/main as we are missing a bunch of
 # configuration files that are supposed to be available, therefore
-# provide the main functions we need for successfull execution of the
+# provide the main functions we need for successful execution of the
 # decrypt function
 
 timestamp_replacementchars='' # unset by default

testsuite/ngcp-network

@@ -47,7 +47,7 @@ assertEqualFiles() {
 }
 
 
-# make sure ip/netmask/interface can be set on exisiting host
+# make sure ip/netmask/interface can be set on existing host
 ${CMD} --input-file=network-config/network_pro.yml --output-file=testfiles/eth42.yml \
        --host=sp1 --set-interface=eth42 --ip=1.2.3.4 --netmask=255.255.255.248
 assertEqualFiles testfiles/eth42.yml network-config/eth42.yml