Fix several typos in content docs

content/8.x/developer/extensions/frontend/examples/add-sidebar-widget.adoc

@@ -166,7 +166,7 @@ It will watch for changes and auto rebuild every time the code changes.
 
 === 1.6 - Configure the component to be used on a module
 
-All the previous steps made our new widget avaible and ready to use. We now need to change the view configuration to show it.
+All the previous steps made our new widget available and ready to use. We now need to change the view configuration to show it.
 Lets say that you would like to add your new `hello-world` component to the Accounts module on the record view.
 
 For that you would need to edit the Account's detailviewdefs on `public/legacy/modules/Accounts/metadata/detailviewdefs.php`.

content/admin/administration-panel/Developer Tools.adoc

@@ -147,7 +147,7 @@ For a package to be uninstallable it needs to be defined as uninstallable in the
  package manifest file. For more information regarding the manifest file 
 see the link:../../../developer/module-installer[Developer Guide] 
 
-Unistall a package by clicking the buttons next to the 
+Uninstall a package by clicking the buttons next to the
 package name. 
 
 As with the install procedure, you will be asked 

content/admin/administration-panel/Emails/Email.adoc

@@ -233,7 +233,7 @@ Cases will be assigned randomly to members of the specified group or role.
 If *SuiteCRM* has been configured to auto-create cases, you can select or create an
 link:../../../user/core-modules/emailtemplates[email template] to use as an automated response to
 notify the sender that a case has been created. If no template is specified here, this automated
-repsonse will not be sent. image:EmailAutoReplyConfiguration.png[New Case Auto-Reply template]
+response will not be sent. image:EmailAutoReplyConfiguration.png[New Case Auto-Reply template]
 
 [cols="20,80", frame = "none", grid = "none"]
 |===

content/admin/administration-panel/Google Sync.adoc

@@ -96,7 +96,7 @@ Click on the 'Choose File' button here, and select the JSON file you downloaded
 Click the ‘Save’ button at the bottom of the screen.|image:cred_14.png[float=left]
 
 |This will return you to the 'Administration' menu. Go back into 'Google Calendar Settings'. +
-Now it says 'Configured' in green to show that the JSON file has been successfuly saved.|image:cred_15.png[float=left]
+Now it says 'Configured' in green to show that the JSON file has been successfully saved.|image:cred_15.png[float=left]
 
 |===
 

content/blog/creating-custom-field-types.adoc

@@ -120,4 +120,4 @@ and one for the Edit View at
 After a quick repair and rebuild (and assuming the field has been added
 to the views), you’ll see the new field:
 
-image:04ColourPicker.png[Colour Picker Exmaple]
+image:04ColourPicker.png[Colour Picker Example]

content/blog/creating-custom-field-types.ru.adoc

@@ -120,4 +120,4 @@ and one for the Edit View at
 After a quick repair and rebuild (and assuming the field has been added
 to the views). You’ll see the new field:
 
-image:04ColourPicker.png[Colour Picker Exmaple]
+image:04ColourPicker.png[Colour Picker Example]

content/blog/larger-upgrades.adoc

@@ -87,7 +87,7 @@ Processes Designs, test cases?
 - Do any *add-ons* need updating? Are they compatible with the new SuiteCRM?
 - Did you use any *custom changes* done in a non-upgrade-safe way, editing files in core, instead of using established
 customization mechanisms? These will need to be redone.
-- Any SuiteR-specifc *Theme customizations* will need to be redone for SuiteP Theme.
+- Any SuiteR-specific *Theme customizations* will need to be redone for SuiteP Theme.
 
 === Align with your organization 
 

content/community/contributing-to-docs/guidelines.adoc

@@ -103,7 +103,7 @@ to be used in pages that have a sub-directory. (This is a shorcode provided by l
 {{%/* children depth="3" showhidden="true" */%}}
 ----
 - Including an automatically generated *List of GitHub Contributors* (for the *Release Notes* pages). You can 
-list an indefinte number of contributors. (This is a shortcode 
+list an indefinite number of contributors. (This is a shortcode
 link:https://github.com/salesagility/SuiteDocs/blob/master/layouts/shortcodes/ghcontributors.html[defined in our own site^]), 
 and can serve as an example if you want to create others).
 

content/developer/api/Developer-setup-guide/JSON-API.adoc

@@ -40,7 +40,7 @@ sudo chown www-data:www-data p*.key
 
 === OAUTH2 encryption key
 OAuth2’s AuthorizationServer needs to set an encryption key for security reasons.
-This key has been gererated during the SuiteCRM installation and stored in the config.php under "oauth2_encryption_key".
+This key has been generated during the SuiteCRM installation and stored in the config.php under "oauth2_encryption_key".
 If you would like to change its value you may generate a new one by running
 [source,php]
 php -r 'echo base64_encode(random_bytes(32)), PHP_EOL;'

content/developer/api/JSON API Error Object.adoc

@@ -34,14 +34,14 @@ $error = new JsonApiErrorObject(
     // status: the HTTP status code applicable to this problem, expressed as a string value.
     STATUS,                                     
     // links: a links object
-    ['about' => 'Descrioption about the problem'],          
+    ['about' => 'Description about the problem'],
     // source: an object containing references to the source of the error
     ['pointer' => '/test/foo/bar', 'parameter' => 'wrong'], 
     // meta: a meta object containing non-standard meta-information about the error.
     ['some' => 'meta info']                     
 );
 
-// retriving Error Object from an Exception:
+// retrieving Error Object from an Exception:
 try {
   // ...do stuff
 } catch (Exception $e) {