From 3d40a606f78f6b13e7617ad8eaea6d32801d73a3 Mon Sep 17 00:00:00 2001
From: Alexis Sellier <self@cloudhead.io>
Date: Thu, 6 Apr 2023 15:39:04 +0200
Subject: [PATCH] cli: Fix `rad track` help output

Even though we accept `did:key` as a substitute for NIDs, we don't
generally accept DIDs in this command.
---
 radicle-cli/src/commands/track.rs | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/radicle-cli/src/commands/track.rs b/radicle-cli/src/commands/track.rs
index 98c43dba..b742e80e 100644
--- a/radicle-cli/src/commands/track.rs
+++ b/radicle-cli/src/commands/track.rs
@@ -16,11 +16,11 @@ pub const HELP: Help = Help {
     usage: r#"
 Usage
 
-    rad track <did> [--[no-]fetch] [--alias <name>] [<option>...]
+    rad track <nid> [--[no-]fetch] [--alias <name>] [<option>...]
     rad track <rid> [--[no-]fetch] [--scope <scope>] [<option>...]
 
-    The `track` command takes either a DID or an RID. Based on the argument, it will
-    either update the tracking policy of a node (DID), or a repository (RID).
+    The `track` command takes either an NID or an RID. Based on the argument, it will
+    either update the tracking policy of a node (NID), or a repository (RID).
 
     When tracking a repository, a scope can be specified: this can be either `all` or
     `trusted`. When using `all`, all remote nodes will be tracked for that repository.
@@ -107,7 +107,7 @@ impl Args for Options {
 
         Ok((
             Options {
-                op: op.ok_or_else(|| anyhow!("either a DID or an RID must be specified"))?,
+                op: op.ok_or_else(|| anyhow!("either a NID or an RID must be specified"))?,
                 fetch,
                 verbose,
             },