From 7477d15ee55d614ff34c5fe65330be7da13fa9b4 Mon Sep 17 00:00:00 2001 From: Arseniy Kuznetsov Date: Sun, 24 Jan 2021 14:26:44 +0100 Subject: [PATCH] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 9e8cf80..6523af1 100644 --- a/README.md +++ b/README.md @@ -89,7 +89,7 @@ MKTXP only needs ```API``` and ```Read```, so at that point you can go to your r ``` ## A check on reality -Now let's put some Mikrotik device address / user credentials in the above MKTXP configuration file, and at that point we should already be able to check our progress so far. Since MKTXP can output selected metrics directly on the command line with the ````mktxp print```` command, it's easy to check on things even before connecting MKTXP to Prometheus or Grafana. \ +Now let's put some Mikrotik device address / user credentials in the above MKTXP configuration file, and at that point we should already be able to check out on our progress so far. Since MKTXP can output selected metrics directly on the command line with the ````mktxp print```` command, it's easy to check on things even before connecting MKTXP to Prometheus or Grafana. \ For example, let's go take a look at some of my smart home CAPsMAN clients: ``` ~> mktxp print -en MKT-GT -cc