use present

Author: jpinsonneau

content/posts/2025-01-23-cli_whats_new_1.8.md

@@ -18,15 +18,15 @@ authors: [jpinsonneau]
 ------------------------------------------------------------------------
 ```
 
-Since we [introduced the Network Observability CLI](./2024-07-25-cli.md), numerous features have been added. This article will cover the improvements in version 1.8 and provide some concrete examples.
+Since we [introduced the Network Observability CLI](./2024-07-25-cli.md), numerous features have been added. This article covers the improvements in version 1.8 and provide some concrete examples.
 
 ## New Options Available
 This update adds several options to the CLI, covering more scenarios and enabling scripting on top of the tool.
 
 ### Operate in the Background
 The `--background` option allows you to start a flow or packet capture without connecting your terminal to the **collector pod**. This enables you to let the capture run in the background while you work on something else. 
 You can check the capture's progress using the `follow` command.
-The capture will end automatically when either maximum bytes (50MB) or time (5m) is reached. You can update these accordingly using the `--max-bytes` and `--max-time` options.
+The capture is ending automatically when either maximum bytes (50MB) or time (5m) is reached. You can update these accordingly using the `--max-bytes` and `--max-time` options.
 The `stop` command also allows you to end the capture manually.
 In both cases, the collector pod keeps running to let you download the output locally using the `copy` command.
 Once the job is complete, you `cleanup` everything.
@@ -44,16 +44,16 @@ oc netobserv cleanup            # Remove all
 ```
 
 ### Customizable Namespace
-You can now customize the capture namespace using the `NETOBSERV_NAMESPACE` environment variable. When the CLI starts, it automatically checks if this namespace exists and will stop if it finds any conflict with a pending capture. This is particularly useful if you want to run captures in parallel.
+You can now customize the capture namespace using the `NETOBSERV_NAMESPACE` environment variable. When the CLI starts, it automatically checks if this namespace exists and stops if it finds any conflict with a pending capture. This is particularly useful if you want to run captures in parallel.
 
 ```sh
 NETOBSERV_NAMESPACE=my_ns oc netobserv [flows|packets|metrics|follow|stop|copy|cleanup]
 ```
 
 ### Subnets Labelling (for OCP clusters)
-The tool can now read OpenShift configurations from `cluster-config-v1` and `network` to identify **Machine**, **Pods**, and **Services** subnets using the `--get-subnets` option. This will automatically add `SrcSubnetLabel` and `DstSubnetLabel` to your flows.
+The tool can now read OpenShift configurations from `cluster-config-v1` and `network` to identify **Machine**, **Pods**, and **Services** subnets using the `--get-subnets` option. This automatically adds `SrcSubnetLabel` and `DstSubnetLabel` to your flows.
 
-You will see subnets being configured during the creation of the agents:
+You can see subnets being configured during the creation of the agents:
 ```sh
 creating flow-capture agents:
 opt: get_subnets, value: true
@@ -81,7 +81,7 @@ oc netobserv flows \              # Capture flows
 or --protocol=UDP                 # or UDP
 ```
 
-You will see filters being validated during the creation of the agents:
+You can see filters being validated during the creation of the agents:
 ```sh
 creating flow-capture agents:
 opt: filter_protocol, value: TCP
@@ -97,7 +97,7 @@ You can add up to 16 sets of filters separated by the `or` operator to create mu
 ### Regular Expressions Usage
 If you need to filter on enriched content beyond the agent-level filters, you can use **regexes** to match any field/value pair. To keep only the traffic from OpenShift namespaces, for example, you can use `--regexes=SrcK8S_Namespace~openshift.*`.
 
-You will see regexes being validated during the creation of the agents:
+You see regexes being validated during the creation of the agents:
 ```sh
 creating flow-capture agents:
 opt: filter_regexes, value: SrcK8S_Namespace~openshift.*
@@ -109,7 +109,7 @@ key: SrcK8S_Namespace value: openshift.*
 Regexes are comma-separated, so you can use multiple at once, such as `--regexes=SrcK8S_Namespace~my-ns,SrcK8S_Name~my-app`. Refer to the [flows format](https://github.com/netobserv/network-observability-operator/blob/main/docs/flows-format.adoc) to see the possible fields.
 
 ## Unified Collector User Experience
-All filtering capabilities are now supported for **packets** capture and will display enriched data while collecting. This improvement was made possible by introducing the [flowlogs-pipeline](https://github.com/netobserv/flowlogs-pipeline) component inside [eBPF agents](https://github.com/netobserv/netobserv-ebpf-agent), which parses packets and generates flows from them.
+All filtering capabilities are now supported for **packets** capture and displays enriched data while collecting. This improvement was made possible by introducing the [flowlogs-pipeline](https://github.com/netobserv/flowlogs-pipeline) component inside [eBPF agents](https://github.com/netobserv/netobserv-ebpf-agent), which parses packets and generates flows from them.
 
 Run a packet capture on a specific port for example:
 ```sh
@@ -129,12 +129,12 @@ oc netobserv metrics --enable_pktdrop
 ```
 to focus only on drops.
 
-On top of the features, you can use all the filtering capabilities mentioned above to focus on what you're looking for. A `NetObserv / On Demand` dashboard will be automatically created, showing the results.
+On top of the features, you can use all the filtering capabilities mentioned above to focus on what you're looking for. A `NetObserv / On Demand` dashboard is automatically created, showing the results.
 
 ![dashboard]({page.image('cli-whats-new-1-8/dashboard.png')})
 
 In this mode, the maximum bytes or time options are ignored since there is no collector pod involved. Only the eBPF agents are deployed. 
-You will need to run `stop` or `cleanup` command to remove everything.
+You need to run `stop` or `cleanup` command to remove everything.
 
 ## Help!