Fix typos in doc

sucessful ==> successful
Unsucessful ==> Unsuccessful
absense ==> absence
authenicator ==> authenticator
colummn ==> column
chosing ==> choosing
speficiation ==> specification
representating ==> representing
remebering ==> remembering

Author: fkmy

doc/argon2.rdoc

@@ -38,7 +38,7 @@ from transitioning from bcrypt to argon2 and vice-versa, if you are using the
 update_password_hash feature.
 
 Argon2 is more configurable than bcrypt in terms of password hash cost
-speficiation.  Instead of specifying the password_hash_cost value as
+specification.  Instead of specifying the password_hash_cost value as
 an integer, you must specify the password hash cost as a hash, such as
 (<tt>{t_cost: 2, m_cost: 16}</tt>).
 

doc/base.rdoc

@@ -27,7 +27,7 @@ account_id_column :: The primary key column of the +accounts_table+.
 account_open_status_value :: The integer representing open accounts.
 account_select :: An array of columns to select from +accounts_table+. By default, selects all columns in the table.
 account_status_column :: The status id column in the +accounts_table+.
-account_unverified_status_value :: The integer representating unverified accounts.
+account_unverified_status_value :: The integer representing unverified accounts.
 authenticated_by_session_key :: The key in the session hash storing an array of methods used to authenticate.
 autocomplete_for_field?(param) :: Whether to use an autocomplete attribute for the given parameter, defaults to +mark_input_fields_with_autocomplete?+.
 autologin_type_session_key :: The key in the session hash storing the type of autologin method used, if autologin was used to authenticate.

doc/change_login.rdoc

@@ -10,7 +10,7 @@ change_login_button :: The text to use for the change login button.
 change_login_error_flash :: The flash error to show for an unsuccessful login change.
 change_login_notice_flash :: The flash notice to show after a successful login change.
 change_login_page_title :: The page title to use on the change login form.
-change_login_redirect :: Where to redirect after a sucessful login change.
+change_login_redirect :: Where to redirect after a successful login change.
 change_login_requires_password? :: Whether a password is required when changing logins.
 change_login_route :: The route to the change login action. Defaults to +change-login+.
 same_as_current_login_message :: The error message to display if using the same value as the current login when changing the login.

doc/change_password.rdoc

@@ -10,7 +10,7 @@ change_password_button :: The text to use for the change password button.
 change_password_error_flash :: The flash error to show for an unsuccessful password change.
 change_password_notice_flash :: The flash notice to show after a successful password change.
 change_password_page_title :: The page title to use on the change password form.
-change_password_redirect :: Where to redirect after a sucessful password change.
+change_password_redirect :: Where to redirect after a successful password change.
 change_password_requires_password? :: Whether a password is required when changing passwords.
 change_password_route :: The route to the change password action. Defaults to +change-password+.
 invalid_previous_password_message :: The message to use when the previous password was incorrect.  Defaults to +invalid_password_message+.

doc/guides/alternative_login.rdoc

@@ -15,7 +15,7 @@ does not expect an email address to be provided.
 Note that Rodauth features that require sending email need an email address, and
 that defaults to the value of the login column.  If you have both a username and
 an email for an account, you can have the login column be the user, and use the
-value of the email colummn for the email address.
+value of the email column for the email address.
 
   plugin :rodauth do
     enable :login, :logout, :reset_password

doc/guides/delay_password.rdoc

@@ -11,7 +11,7 @@ ask the user to set their password only when they verify their account:
 Note that this is already the default behaviour when verify account feature is
 loaded, but it's not when verify account grace period is used, because it would
 prevent the account from logging in during the grace period. You can work around
-this by automatically remebering their login during account creation using the
+this by automatically remembering their login during account creation using the
 remember feature.  Be aware that remembering accounts has effects beyond the
 verification period, and this would only allow automatic logins from the browser
 that created the account.

doc/guides/internals.rdoc

@@ -210,7 +210,7 @@ Here's a heavily commented example showing what is going on inside a Rodauth fea
             set_notice_flash foo_notice_flash
             redirect foo_redirect
           else
-            # Unsucessful form subsmission will usually set the error flash,
+            # Unsuccessful form subsmission will usually set the error flash,
             # the redisplay the page so that the submission can be fixed.
             set_error_flash foo_error_flash
             foo_view

doc/login.rdoc

@@ -20,7 +20,7 @@ login_form_footer_links :: An array of entries for links to show on the login pa
 login_form_footer_links_heading :: A heading to show before the login form footer links.
 login_notice_flash :: The flash notice to show after successful login.
 login_page_title :: The page title to use on the login form.
-login_redirect :: Where to redirect after a sucessful login.
+login_redirect :: Where to redirect after a successful login.
 login_redirect_session_key :: The key in the session hash storing the location to redirect to after successful login.
 login_return_to_requested_location? :: Whether to redirect to the originally requested location after successful login when +require_login+ was used, false by default.
 login_return_to_requested_location_max_path_size :: The maximum path size in bytes to allow when returning to requested location, 2048 by default to avoid exceeding the 4K cookie size limit

doc/otp.rdoc

@@ -53,7 +53,7 @@ otp_setup_notice_flash :: The flash notice to show if OTP authentication setup w
 otp_setup_page_title :: The page title to use on the form to setup OTP authentication.
 otp_setup_param :: The parameter name used for the OTP secret when setting up OTP authentication.
 otp_setup_raw_param :: The parameter name used for the raw OTP secret when setting up OTP authentication, when +otp_keys_use_hmac?+ is true. 
-otp_setup_redirect :: Where to redirect after sucessful OTP authentication setup.
+otp_setup_redirect :: Where to redirect after successful OTP authentication setup.
 otp_setup_route :: The route to the OTP setup action. Defaults to +otp-setup+.
 
 == Auth Methods

doc/password_complexity.rdoc

@@ -3,7 +3,7 @@
 The password complexity feature implements more sophisticated password
 complexity checks.  It is not recommended to use this feature unless
 you have a policy that requires it, as users that would not choose a
-good password in the absense of password complexity requirements are
+good password in the absence of password complexity requirements are
 unlikely to choose a good password if you have password complexity
 requirements.
 

doc/password_expiration.rdoc

@@ -13,7 +13,7 @@ enabled, but it can be enabled by setting +allow_password_change_after+
 to a positive number of seconds.
 
 It is not recommended to use this feature unless you have a policy that
-requires it, as password expiration in general results in users chosing
+requires it, as password expiration in general results in users choosing
 weaker passwords.  When asked to change their password, many users choose
 a password that is based on their previous password, so forcing password
 expiration is in general a net loss from a security perspective.

doc/release_notes/2.32.0.txt

@@ -38,7 +38,7 @@
     which can be used to handle cases where a user successfully
     authenticated via TOTP using the old secret.  This can be used
     to direct them to a page to remove the TOTP authenticator and
-    then setup a new TOTP authenicator.
+    then setup a new TOTP authenticator.
 
 * Many *_response configuration methods have been added, which allow
   users to override Rodauth's default behavior in successful cases of