Merge pull request #6355 from hustrust/master

chore: fix some typos in comment

Author: carbolymer

cardano-node/src/Cardano/Node/Tracing/Consistency.hs

@@ -125,7 +125,7 @@ checkNodeTraceConfiguration' trConfig =
     getAllNamespaces
 
 
--- | Returns a list of all namepsaces from all tracers
+-- | Returns a list of all namespaces from all tracers
 getAllNamespaces :: [([T.Text],[T.Text])]
 getAllNamespaces =
     -- NodeInfo tracer

cardano-node/test/Test/Cardano/Tracing/OrphanInstances/HardFork.hs

@@ -3,7 +3,7 @@
 -- The golden files are stored in the path given by 'addPrefix'.
 --
 -- If a new test is added and no golden file exists for it it will be created.
--- This new file needs to be commited.
+-- This new file needs to be committed.
 --
 -- For now we added a couple of representative examples, however the tests are
 -- not exhaustive.

nix/nixos/cardano-tracer-service-workbench.nix

@@ -48,7 +48,7 @@ let serviceConfigToJSON =
         } // (cfg.prometheus or {});
         # Just an example for metrics compatibility mapping.
         # An entry means the first entry has the second entry as alias.
-        # The Metrics is then avalable, both with the original and the mapped name.
+        # The Metrics is then available, both with the original and the mapped name.
         # Only one mapping per message is supported.
         # metricsComp = {
         #     "Mempool.TxsInMempool" = "Mempool.TxsInMempool.Mapped";

trace-dispatcher/doc/trace-dispatcher.md

@@ -302,7 +302,7 @@ The configurability of dispatchers provided by this library relies on:
 
 2. __Runtime Reconfigurability__: Triggered by invoking `configureTracers`, enabling changes during program execution.
 
-The usual form to provide a configuration is via a configuration file, wich can be in JSON or YAML format. The options that
+The usual form to provide a configuration is via a configuration file, which can be in JSON or YAML format. The options that
 can be given based on a namespace are: `severity`, `detail`, `backends` and `limiter`.
 
 Backends can be a combination of `Forwarder`, `EKGBackend`, `PrometheusSimple [suffix|nosuffix] [bindhost] <port>` and
@@ -677,7 +677,7 @@ checkNodeTraceConfiguration ::
   -> IO [Text]
 ```
 
-An example text is "Config namespace error: i.am.an.invalid.namepace" .
+An example text is "Config namespace error: i.am.an.invalid.namespace" .
 
 This check is performed within a `cardano-node` test case (`Test.Cardano.Tracing.NewTracing.Consistency.tests`), ensuring that it is automatically verified with each pull request.
 

trace-forward/src/Trace/Forward/Forwarding.hs

@@ -174,7 +174,7 @@ launchForwarders iomgr magic
                  ekgStore sink dpStore tracerSocketMode maxReconnectDelay =
   -- If 'tracerSocketMode' is not specified, it's impossible to establish
   -- network connection with acceptor application (for example, 'cardano-tracer').
-  -- In this case, we should not lauch forwarders.
+  -- In this case, we should not launch forwarders.
   case tracerSocketMode of
     Nothing -> return ()
     Just (socketPath, mode) ->