docs: fix broken kubernetes links (#8531)

* docs: fix broken kubernetes links

Refs: #8530

* docs: adjust href link texts for persistent volume and service account files as deployment file

* docs: fix grammar issues and highlight links for visibility

Co-authored-by: Kevin Martens <[email protected]>

---------

Co-authored-by: Kevin Martens <[email protected]>

Author: EmirBoyaci

content/doc/book/installing/_kubernetes.adoc

@@ -43,7 +43,7 @@ We choose to use the `/data` directory. This directory will contain our Jenkins
 
 *We will create a volume which is called jenkins-pv:*
 
-. Paste the content from link:https://raw.githubusercontent.com/jenkins-infra/jenkins.io/master/content/doc/tutorials/kubernetes/installing-jenkins-on-kubernetes/jenkins-01-volume.yaml[https://raw.githubusercontent.com/installing-jenkins-on-kubernetes/jenkins-01-volume.yaml] into a YAML formatted file called `jenkins-01-volume.yaml`.
+. Paste the content from the link:https://raw.githubusercontent.com/jenkins-infra/jenkins.io/master/content/doc/tutorials/kubernetes/installing-jenkins-on-kubernetes/jenkins-01-volume.yaml[persistent volume file] into a YAML formatted file called `jenkins-01-volume.yaml`.
 . Run the following command to apply the spec:
 +
 [source,bash]
@@ -96,7 +96,7 @@ A RoleBinding may reference any Role in the same namespace.
 Alternatively, a RoleBinding can reference a ClusterRole and bind that ClusterRole to the namespace of the RoleBinding.
 To bind a ClusterRole to all the namespaces in our cluster, we use a ClusterRoleBinding.
 
-. Paste the content from link:https://raw.githubusercontent.com/jenkins-infra/jenkins.io/master/content/doc/tutorials/kubernetes/installing-jenkins-on-kubernetes/jenkins-02-sa.yaml[https://raw.githubusercontent.com/installing-jenkins-on-kubernetes/jenkins-02-sa.yaml] into a YAML formatted file called
+. Paste the content from the link:https://raw.githubusercontent.com/jenkins-infra/jenkins.io/master/content/doc/tutorials/kubernetes/installing-jenkins-on-kubernetes/jenkins-02-sa.yaml[service account file] into a YAML formatted file called
 `jenkins-02-sa.yaml`.
 +
 . Run the following command to apply the spec:
@@ -282,9 +282,9 @@ The YAML files are easily tracked, edited, and can be reused indefinitely.
 
 === Create Jenkins deployment file
 
-Copy the contents link:https://raw.githubusercontent.com/jenkins-infra/jenkins.io/master/content/doc/tutorials/kubernetes/installing-jenkins-on-kubernetes/jenkinsHelm-03-deployment.yaml[here] into your preferred text editor and create a jenkinsHelm-03-deployment.yaml file in the “jenkins” namespace we created in this link:/doc/book/installing/kubernetes/#create-a-namespace[section] above.
+Copy the contents from link:https://raw.githubusercontent.com/jenkins-infra/jenkins.io/master/content/doc/tutorials/kubernetes/installing-jenkins-on-kubernetes/jenkins-03-deployment.yaml[this file] into your preferred text editor and create a jenkins-03-deployment.yaml file in the “jenkins” namespace we created in the link:/doc/book/installing/kubernetes/#create-a-namespace[above section].
 
-* This link:https://raw.githubusercontent.com/jenkins-infra/jenkins.io/master/content/doc/tutorials/kubernetes/installing-jenkins-on-kubernetes/jenkinsHelm-03-deployment.yaml[deployment file] is defining a Deployment as indicated by the `kind` field.
+* This link:https://raw.githubusercontent.com/jenkins-infra/jenkins.io/master/content/doc/tutorials/kubernetes/installing-jenkins-on-kubernetes/jenkins-03-deployment.yaml[deployment file] is defining a Deployment as indicated by the `kind` field.
 * The Deployment specifies a single replica. This ensures one and only one instance
 will be maintained by the Replication Controller in the event of failure.
 * The container image name is `jenkins` and version is a floating tag `lts-jdk21`
@@ -310,7 +310,7 @@ To create the deployment execute:
 
 [source,bash]
 ----
-kubectl create -f jenkinsHelm-03-deployment.yaml -n jenkins
+kubectl create -f jenkins-03-deployment.yaml -n jenkins
 ----
 
 The command also instructs the system to install Jenkins within the jenkins namespace.
@@ -334,9 +334,9 @@ It allows us to maintain a persistent connection to the pod regardless of the ch
 With a local deployment, this means creating a NodePort service type.
 A NodePort service type exposes a service on a port on each node in the cluster.
 The service is accessed through the Node IP address and the service nodePort.
-A simple service is defined link:https://raw.githubusercontent.com/jenkins-infra/jenkins.io/master/content/doc/tutorials/kubernetes/installing-jenkins-on-kubernetes/jenkinsHelm-04-service.yaml[here]:
+A simple service is defined link:https://raw.githubusercontent.com/jenkins-infra/jenkins.io/master/content/doc/tutorials/kubernetes/installing-jenkins-on-kubernetes/jenkins-04-service.yaml[in this file]:
 
-* This link:https://raw.githubusercontent.com/jenkins-infra/jenkins.io/master/content/doc/tutorials/kubernetes/installing-jenkins-on-kubernetes/jenkinsHelm-04-service.yaml[service file] is defining a Service as
+* This link:https://raw.githubusercontent.com/jenkins-infra/jenkins.io/master/content/doc/tutorials/kubernetes/installing-jenkins-on-kubernetes/jenkins-04-service.yaml[service file] is defining a Service as
 indicated by the `kind` field.
 * The Service is of type NodePort. Other options are ClusterIP (only accessible within the cluster) and LoadBalancer (IP address assigned by a cloud provider e.g. AWS Elastic IP).
 * The list of ports specified within the spec is a list of ports exposed by this service.
@@ -348,7 +348,7 @@ To create the service execute:
 
 [source,bash]
 ----
-kubectl create -f jenkinsHelm-04-service.yaml -n jenkins
+kubectl create -f jenkins-04-service.yaml -n jenkins
 ----
 
 To validate that creating the service was successful you can run: