s/Internet Secure/InternetSecure

1 files changed, 6 insertions, 6 deletions

diff --git a/InternetSecure.pm b/InternetSecure.pm
index 1280c88..58a6ce7 100755
--- a/InternetSecure.pm
+++ b/InternetSecure.pm
@@ -339,7 +339,7 @@ Business::OnlinePayment::InternetSecure - InternetSecure backend for Business::O
 
 Business::OnlinePayment::InternetSecure is an implementation of
 L<Business::OnlinePayment> that allows for processing online credit card
-payments through Internet Secure.
+payments through InternetSecure.
 
 See L<Business::OnlinePayment> for more information about the generic
 Business::OnlinePayment interface.
@@ -348,7 +348,7 @@ Business::OnlinePayment interface.
 
 Object creation is done via L<Business::OnlinePayment>; see its manpage for
 details.  The I<merchant_id> processor option is required, and corresponds
-to the merchant ID assigned to you by Internet Secure.
+to the merchant ID assigned to you by InternetSecure.
 
 =head1 METHODS
 
@@ -430,7 +430,7 @@ C<CAD> (default) or C<USD>.
 =item taxes
 
 Taxes to be added automatically.  These should not be included in B<amount>;
-they will be automatically added by Internet Secure later on.
+they will be automatically added by InternetSecure later on.
 
 Available taxes are C<GST>, C<PST> and C<HST>.  Taxes can be combined by
 separating them with spaces, such as C<GST HST>.
@@ -481,7 +481,7 @@ following:
 
 =item avs_response() / cvv2_response()
 
-Results of the AVS and CVV2 checks.  See the Internet Secure documentation for
+Results of the AVS and CVV2 checks.  See the InternetSecure documentation for
 the list of possible values.
 
 =item products_raw()
@@ -532,9 +532,9 @@ be left undefined.
 
 =head2 Character encoding
 
-Since communication to/from Internet Secure is encoded with UTF-8, all Unicode
+Since communication to/from InternetSecure is encoded with UTF-8, all Unicode
 characters are theoretically available when submitting information via
-B<submit()>.  (Further restrictions may be imposed by Internet Secure itself.)
+B<submit()>.  (Further restrictions may be imposed by InternetSecure itself.)
 
 When using non-ASCII characters, all data provided to B<submit()> should either
 be in the current native encoding (typically latin-1, unless it was modified