updating number in list and iamge for kibana UI

docs/en/ingest-management/elastic-agent/advanced-kubernetes-managed-by-fleet.asciidoc

@@ -1,24 +1,27 @@
 [[advanced-kubernetes-managed-by-fleet]]
 = Advanced {agent} configuration managed by {fleet}
 
-:manifest: https://raw.githubusercontent.com/elastic/elastic-agent/{branch}/deploy/kubernetes/elastic-agent-managed-kubernetes.yaml
+For basic {agent} managed by {fleet} scenarios follow the steps on <<running-on-kubernetes-managed-by-fleet>> page.
 
-For basic {agent} managed by {fleet} scenarios follow the steps in <<running-on-kubernetes-managed-by-fleet>>.
-
-On managed {agent} installations it can be useful to provide the ability to configure more advanced options, such as the configuration of providers during startup. Refer to <<providers>> for more details.
+On managed {agent} installations could be useful to provide the ability to configure more advanced options like the configuration of providers during the startup. Refer to <<providers>> for more details.
 
 Following steps demonstrate above scenario:
 
 [discrete]
 == Step 1: Download the {agent} manifest
 
-include::run-container-common/download-elastic-agent.asciidoc[]
+It is advisable to follow the steps of <<install-fleet-managed-elastic-agent>> with Kubernetes Integration installed in your policy and download the {agent} manifest from Kibana UI
+
+image::images/k8kibanaUI.png[{agent} with K8s Package manifest]
+
+Notes:: 
+Sample manifests can also be found https://github.com/elastic/elastic-agent/blob/main/deploy/kubernetes/elastic-agent-managed-kubernetes.yaml[here]
 
 [discrete]
 == Step 2: Create a new configmap
 
 [source,yaml]
-.Create a new configmap
+. Create a new configmap
 ------------------------------------------------
 apiVersion: v1
 kind: ConfigMap
@@ -36,46 +39,27 @@ data:
 ------------------------------------------------
 
 Notes:: 
-1. The above example demonstrates how to disable the `kubernetes_leaderelection` provider. For alternative scenarios you can follow the same procedure. For example, the following settings configure the `kubernetes` provider metadata enrichment:
-
-[source,yaml]
-.Example of configmap for kubernetes provider configuration
-------------------------------------------------
-apiVersion: v1
-kind: ConfigMap
-metadata:
-  name: agent-node-datastreams
-  namespace: kube-system
-  labels:
-    k8s-app: elastic-agent
-data:
-  agent.yml: |-
-    providers.kubernetes: 
-      add_resource_metadata: 
-        deployment: true
-        cronjob: true
-    fleet.enabled: true
-    fleet.access_token: "<FLEET_ENROLLMENT_TOKEN>"
----
-------------------------------------------------
-
-Notes:: 
-2. Find more information about https://www.elastic.co/guide/en/fleet/current/fleet-enrollment-tokens.html[Enrollment Tokens].
+1. In the above example the disablement of `kubernetes_leaderelection` provider is demonstrated. Same procedure can be followed for alternative scenarios.
+2. Find more information for https://www.elastic.co/guide/en/fleet/current/fleet-enrollment-tokens.html[Enrollment Tokens].
 
 [discrete]
 == Step 3: Configure Daemonset
 
-Inside the downloaded manifest, update the Daemonset resource:
+Inside the downloaded manifest, update Daemonset resource part:
 
 [source,yaml]
 .Update entrypoint 
 ------------------------------------------------
 containers:
   - name: elastic-agent
-    image: docker.elastic.co/beats/elastic-agent: <Image Version>     #< Change this with the image version of agent
+    image: docker.elastic.co/beats/elastic-agent: <ImageVersion>     
     args: ["-c", "/etc/elastic-agent/agent.yml", "-e"]
 ------------------------------------------------
 
+Notes:: 
+The <ImageVersion> is just a placeholder for the elastic-agent image version that will you will download in your manifest: eg. `image: docker.elastic.co/beats/elastic-agent: 8.11.0`
+Important thing is to update your manifest with args details 
+
 [source,yaml]
 .Add extra Volume Mount 
 ------------------------------------------------
@@ -99,6 +83,6 @@ volumes:
 [discrete]
 == Important Note
 
-By default the manifests for {agent} managed by {fleet} have `hostNetwork:true`. In order to support multiple installations of {agent}s in the same node you should set `hostNetwork:false`. See this relevant https://github.com/elastic/elastic-agent/tree/main/docs/manifests/hostnetwork[example] as described in https://github.com/elastic/elastic-agent/blob/main/docs/elastic-agent-ksm-sharding.md[{agent} Manifests in order to support Kube-State-Metrics Sharding].
+By default the manifests for {agent} managed by {fleet} have `hostNetwork:true`. In order to support multiple installations of {agent}s in the same node you should set `hostNetwork:false`. See relevant https://github.com/elastic/elastic-agent/tree/main/docs/manifests/hostnetwork[example] as described in https://github.com/elastic/elastic-agent/blob/main/docs/elastic-agent-ksm-sharding.md[{agent} Manifests in order to support Kube-State-Metrics Sharding]