fix(docs): Fixed various letter casing and script errors

Signed-off-by: Łukasz Jernaś <lukasz.jernas@allegro.com>

docs/features/kubernetes/installation.md

@@ -96,6 +96,7 @@ async function main() {
   // ...
   /* highlight-add-next-line */
   apiRouter.use('/kubernetes', await kubernetes(kubernetesEnv));
+}
 ```
 
 That's it! The Kubernetes frontend and backend have now been added to your

docs/features/software-catalog/configuration.md

@@ -31,7 +31,7 @@ catalog (`UrlReaderProcessor`), so no processor configuration is needed. This
 processor _does however_ need an [integration](../../integrations/index.md) to
 understand how to retrieve a given URL. For the example above, you would need to
 configure the [GitHub integration](../../integrations/github/locations.md) to
-read files from github.com.
+read files from GitHub.com.
 
 The locations added through static configuration cannot be removed through the
 catalog locations API. To remove these locations, you must remove them from the

docs/features/software-catalog/external-integrations.md

@@ -543,6 +543,7 @@ export class UserEntityProvider implements EntityProvider {
         locationKey: 'hr-user-https://www.hrurl.com/',
       })),
     })
+  }
 }
 
 ```

docs/features/software-templates/builtin-actions.md

@@ -82,16 +82,16 @@ allow most templates built for `fetch:cookiecutter` to work without any changes.
 ```yaml title="template.yaml"
 steps:
    - id: fetch-base
-   name: Fetch Base
-   # highlight-remove-next-line
-   action: fetch:cookiecutter
-   # highlight-add-next-line
-   action: fetch:template
-   input:
-      url: ./skeleton
-      # highlight-add-next-line
-      cookiecutterCompat: true
-      values:
+     name: Fetch Base
+     # highlight-remove-next-line
+     action: fetch:cookiecutter
+     # highlight-add-next-line
+     action: fetch:template
+     input:
+        url: ./skeleton
+        # highlight-add-next-line
+        cookiecutterCompat: true
+        values:
 ```
 
 ### Manual migration

docs/features/software-templates/dry-run-testing.md

@@ -4,7 +4,7 @@ title: Dry Run Testing
 description: How to enable and implement dry run testing in actions
 ---
 
-Scaffolder templates can be tested using the dry run feature of scaffolder actions. This allows you to simulate the effects of running a scaffolder action without making any actual changes to your environment, for example creating a webhook in Github. Once dry run is enabled in the scaffolder action, you can add handling to actions you use in your scaffolder templates to define how an action should operate in a dry run scenario.
+Scaffolder templates can be tested using the dry run feature of scaffolder actions. This allows you to simulate the effects of running a scaffolder action without making any actual changes to your environment, for example creating a webhook in GitHub. Once dry run is enabled in the scaffolder action, you can add handling to actions you use in your scaffolder templates to define how an action should operate in a dry run scenario.
 
 ## Enabling dry run testing
 

docs/features/software-templates/migrating-to-rjsf-v5.md

@@ -44,7 +44,7 @@ It's possible that if you have a hard dependency on any of the `@rjsf/*` librari
 /* highlight-remove-next-line */
 import { FieldValidation } from '@rjsf/core';
 /* highlight-add-next-line */
-import { FieldValidation } from '@rjsf/utils;
+import { FieldValidation } from '@rjsf/utils';
 ```
 
 ## Escape hatch