diff --git a/configure/logging/kubernetes-logs.md b/configure/logging/kubernetes-logs.md
index bcbcc41e0..bd6c5da8a 100644
--- a/configure/logging/kubernetes-logs.md
+++ b/configure/logging/kubernetes-logs.md
@@ -78,7 +78,6 @@ For long term storage of SUSE Observability log data, it's advised that you set
 For more details of how this can be done, check:
 
 * Shipping logs with [Fluentd \(fluentd.org\)](https://docs.fluentd.org/container-deployment/kubernetes)
-* A complete overview of setting up [log aggregation into Elasticsearch \(bitnami.com\)](https://docs.bitnami.com/tutorials/integrate-logging-kubernetes-kibana-elasticsearch-fluentd/)
 
 ## See also
 
diff --git a/setup/data-management/backup_restore/configuration_backup.md b/setup/data-management/backup_restore/configuration_backup.md
index 387dd8ba9..443bf9300 100644
--- a/setup/data-management/backup_restore/configuration_backup.md
+++ b/setup/data-management/backup_restore/configuration_backup.md
@@ -16,10 +16,10 @@ The configuration backup is enabled by default. In its default setup it will mak
 
 Scripts to work with configuration backups (but also all other backups) can be downloaded from the [latest release for the SUSE Observability Helm chart](https://github.com/StackVista/helm-charts/releases/latest). Download and extract the `backup-scripts-<version>.tar.gz` to get started.
 
-**Before you use the scripts, ensure that** the `kubectl` binary is installed and it is configured with the context and namespace where SUSE Observability is installed. For example run this command to connect to the context `observability-cluster` and namespace `suse-observablity`:
+**Before you use the scripts, ensure that** the `kubectl` binary is installed and it is configured with the context and namespace where SUSE Observability is installed. For example run this command to connect to the context `observability-cluster` and namespace `suse-observability`:
 ```
 kubectl config use-context observability-cluster
-kubectl config set-context --current --namespace=suse-observablity
+kubectl config set-context --current --namespace=suse-observability
 ```
 
 The command line tools to interact with the backups all work by creating a Kubernetes job in the cluster and interacting with that job. After the tool is done the job is automatically removed. Starting the job can take some time (pulling the docker image, scheduling the job in the cluster, etc, all take some time), so the commands will not produce a result immediately.
diff --git a/setup/install-stackstate/troubleshooting.md b/setup/install-stackstate/troubleshooting.md
index e948adb35..4160ab8bd 100644
--- a/setup/install-stackstate/troubleshooting.md
+++ b/setup/install-stackstate/troubleshooting.md
@@ -30,12 +30,12 @@ Here is a quick guide for troubleshooting the startup of SUSE Observability:
    For pods with state `ImagePullBackOff` also check the exact error message, common causes are:
    * An incorrect username/password used to pull the images
    * Connecting to the docker registry failed, this can be due to authentication issues or connectivity issues (firewalls, air-gapped installations)
-   * A typo in the overriden docker image registry URL
+   * A typo in the overridden docker image registry URL
 
    To find out a more detailed cause for the `Pending`, `ImagePullBackOff` or `CrashLoopBackOff` states use this command:
    
    ```text
-   kubectl describe pod<pod-name>
+   kubectl describe pod <pod-name>
    ```
    
    The output contains an `event` section at the end which usually contains the problem. It also has a `State` section for each container that has more details for termination of the container.