Remove old references to "bot instances"

docs/pages/enroll-resources/machine-id/troubleshooting.mdx

@@ -42,8 +42,9 @@ be automatically [locked](../../admin-guides/access-controls/guides/locking.mdx)
 
 Renewable certificates are exclusively stored in the bot's internal data
 directory, by default `/var/lib/teleport/bot`. It's possible to trigger this by
-accident if multiple bots are started using the same internal data directory, or if
-this internal data is otherwise being shared between multiple bot instances.
+accident if multiple bots are started using the same internal data directory, or
+if this internal data is otherwise being shared between multiple `tbot`
+processes.
 
 Additionally, if a bot fails to save its freshly renewed certificates (for
 example, due to a filesystem error) and crashes, it will attempt a renewal
@@ -55,7 +56,7 @@ Before unlocking the bot, try to determine if either of the two scenarios
 described above apply. If the certificates were stolen, there may be
 underlying security concerns that need to be addressed.
 
-Otherwise, first ensure only one bot instance is using the internal data
+Otherwise, first ensure only one `tbot` process is using the internal data
 directory. Multiple bots can be run on a single system, but separate data
 directories must be configured for each.