OCPBUGS-30191: Fixing typos in NetObserv docs

Author: skrthomas

modules/network-observability-flowcollector-api-specifications.adoc

@@ -1244,7 +1244,7 @@ Type::
 
 | `namespace`
 | `string`
-| Namespace where this `LokiStack` resource is located. If omited, it is assumed to be the same as `spec.namespace`.
+| Namespace where this `LokiStack` resource is located. If omitted, it is assumed to be the same as `spec.namespace`.
 
 |===
 == .spec.loki.manual

modules/network-observability-loki-install.adoc

@@ -5,7 +5,7 @@
 :_mod-docs-content-type: PROCEDURE
 [id="network-observability-loki-installation_{context}"]
 = Installing the {loki-op}
-The link:https://catalog.redhat.com/software/containers/openshift-logging/loki-rhel8-operator/622b46bcae289285d6fcda39[{loki-op} versions 5.7+] are the supported {loki-op} versions for Network Observabilty; these versions provide the ability to create a `LokiStack` instance using the `openshift-network` tenant configuration mode and provide fully-automatic, in-cluster authentication and authorization support for Network Observability. There are several ways you can install Loki. One way is by using the {product-title} web console Operator Hub.
+The link:https://catalog.redhat.com/software/containers/openshift-logging/loki-rhel8-operator/622b46bcae289285d6fcda39[{loki-op} versions 5.7+] are the supported {loki-op} versions for Network Observability; these versions provide the ability to create a `LokiStack` instance using the `openshift-network` tenant configuration mode and provide fully-automatic, in-cluster authentication and authorization support for Network Observability. There are several ways you can install Loki. One way is by using the {product-title} web console Operator Hub.
 
 .Prerequisites
 

modules/network-observability-viewing-alerts.adoc

@@ -12,7 +12,7 @@ You can access metrics about health and resource usage of the Network Observabil
 * The `NetObservNoFlows` alert occurs if no flows are ingested for a certain amount of time.
 
 You can also view metrics about the health of the Operator in the following categories:
-+
+
 * *Flows*
 * *Flows Overhead*
 * *Top flow rates per source and destination nodes*

modules/network-observability-working-with-conversations.adoc

@@ -5,7 +5,7 @@
 :_mod-docs-content-type: PROCEDURE
 [id="network-observability-working-with-conversations_{context}"]
 = Working with conversation tracking
-As an administrator, you can you can group network flows that are part of the same conversation. A conversation is defined as a grouping of peers that are identified by their IP addresses, ports, and protocols, resulting in an unique *Conversation Id*. You can query conversation events in the web console. These events are represented in the web console as follows:
+As an administrator, you can group network flows that are part of the same conversation. A conversation is defined as a grouping of peers that are identified by their IP addresses, ports, and protocols, resulting in an unique *Conversation Id*. You can query conversation events in the web console. These events are represented in the web console as follows:
 
 ** *Conversation start*: This event happens when a connection is starting or TCP flag intercepted
 ** *Conversation tick*: This event happens at each specified interval defined in the `FlowCollector` `spec.processor.conversationHeartbeatInterval` parameter while the connection is active.