Merge pull request #24681 from tengqm/links-tutorials

Fix links in tutorials section

Author: k8s-ci-robot

content/en/docs/tutorials/clusters/seccomp.md

@@ -37,7 +37,7 @@ profiles that give only the necessary privileges to your container processes.
 
 In order to complete all steps in this tutorial, you must install
 [kind](https://kind.sigs.k8s.io/docs/user/quick-start/) and
-[kubectl](/doc/tasks/tools/install-kubectl/). This tutorial will show examples
+[kubectl](/docs/tasks/tools/install-kubectl/). This tutorial will show examples
 with both alpha (pre-v1.19) and generally available seccomp functionality, so
 make sure that your cluster is [configured
 correctly](https://kind.sigs.k8s.io/docs/user/quick-start/#setting-kubernetes-version)
@@ -365,4 +365,4 @@ The default seccomp profile should provide adequate access for most workloads.
 Additional resources:
 
 * [A Seccomp Overview](https://lwn.net/Articles/656307/)
-* [Seccomp Security Profiles for Docker](https://docs.docker.com/engine/security/seccomp/)
+* [Seccomp Security Profiles for Docker](https://docs.docker.com/engine/security/seccomp/)

content/en/docs/tutorials/configuration/configure-java-microservice/configure-java-microservice.md

@@ -14,9 +14,9 @@ In this tutorial you will learn how and why to externalize your microservice’s
 ### Creating Kubernetes ConfigMaps & Secrets
 There are several ways to set environment variables for a Docker container in Kubernetes, including: Dockerfile, kubernetes.yml, Kubernetes ConfigMaps, and Kubernetes Secrets.  In the tutorial, you will learn how to use the latter two for setting your environment variables whose values will be injected into your microservices.  One of the benefits for using ConfigMaps and Secrets is that they can be re-used across multiple containers, including being assigned to different environment variables for the different containers.
 
-ConfigMaps are API Objects that store non-confidential key-value pairs.  In the Interactive Tutorial you will learn how to use a ConfigMap to store the application's name.  For more information regarding ConfigMaps, you can find the documentation [here](https://kubernetes.io/docs/tasks/configure-pod-container/configure-pod-configmap/).
+ConfigMaps are API Objects that store non-confidential key-value pairs.  In the Interactive Tutorial you will learn how to use a ConfigMap to store the application's name.  For more information regarding ConfigMaps, you can find the documentation [here](/docs/tasks/configure-pod-container/configure-pod-configmap/).
 
-Although Secrets are also used to store key-value pairs, they differ from ConfigMaps in that they're intended for confidential/sensitive information and are stored using Base64 encoding.  This makes secrets the appropriate choice for storing such things as credentials, keys, and tokens, the former of which you'll do in the Interactive Tutorial.  For more information on Secrets, you can find the documentation [here](https://kubernetes.io/docs/concepts/configuration/secret/).
+Although Secrets are also used to store key-value pairs, they differ from ConfigMaps in that they're intended for confidential/sensitive information and are stored using Base64 encoding.  This makes secrets the appropriate choice for storing such things as credentials, keys, and tokens, the former of which you'll do in the Interactive Tutorial.  For more information on Secrets, you can find the documentation [here](/docs/concepts/configuration/secret/).
 
 
 ### Externalizing Config from Code
@@ -36,4 +36,4 @@ Many open source frameworks and runtimes implement and support MicroProfile Conf
 <!-- lessoncontent -->
 
 ## Example: Externalizing config using MicroProfile, ConfigMaps and Secrets
-### [Start Interactive Tutorial](/docs/tutorials/configuration/configure-java-microservice/configure-java-microservice-interactive/) 
+### [Start Interactive Tutorial](/docs/tutorials/configuration/configure-java-microservice/configure-java-microservice-interactive/) 

content/en/docs/tutorials/hello-minikube.md

@@ -16,25 +16,20 @@ card:
 <!-- overview -->
 
 This tutorial shows you how to run a sample app
-on Kubernetes using [minikube](/docs/setup/learning-environment/minikube) and Katacoda.
+on Kubernetes using minikube and Katacoda.
 Katacoda provides a free, in-browser Kubernetes environment.
 
 {{< note >}}
 You can also follow this tutorial if you've installed minikube locally.
 See [minikube start](https://minikube.sigs.k8s.io/docs/start/) for installation instructions.
 {{< /note >}}
 
-
-
 ## {{% heading "objectives" %}}
 
-
 * Deploy a sample application to minikube.
 * Run the app.
 * View application logs.
 
-
-
 ## {{% heading "prerequisites" %}}
 
 

content/en/docs/tutorials/stateful-application/cassandra.md

@@ -50,7 +50,7 @@ To complete this tutorial, you should already have a basic familiarity with
 ### Additional Minikube setup instructions
 
 {{< caution >}}
-[Minikube](/docs/setup/learning-environment/minikube/) defaults to 1024MiB of memory and 1 CPU.
+[Minikube](https://minikube.sigs.k8s.io/docs/) defaults to 1024MiB of memory and 1 CPU.
 Running Minikube with the default resource configuration results in insufficient resource
 errors during this tutorial. To avoid these errors, start Minikube with the following settings: