remove docs fro newInstance setting that was removed and small tweaks to the docs for the feature

2 files changed, 4 insertions, 6 deletions

diff --git a/docs/guide/index.md b/docs/guide/index.md
index 480ab676..bb536c36 100644
--- a/docs/guide/index.md
+++ b/docs/guide/index.md
@@ -1028,16 +1028,15 @@ The PDB loader comes with a couple configuration options which enable and disabl
 
 ## Launching Binary Ninja from the command line (CLI)
 
-While it has always been possible to launch Binary Ninja from the command line (shell), passing file paths or URLs to open, as of 5.0, it is now possible to have some control over whether it will open in an already running instance of Binary Ninja, or in a new instance. (Previously, this would always start a new Binary Ninja application instance, unless a `binaryninja:` URL was found on the command line.)
+When you launch Binary Ninja from the command-line, you can control whether or not a new window is launched or an existing window is used.
 
-As of version 5.0:
-* Running Binary Ninja from the command line will try to find a running instance in which to open any files or URLs passed on the command line, or activate the main window if no arguments are provided.
+* Running Binary Ninja from the command line will try to find a running instance of the same version in which to open any files or URLs passed on the command line, or activate the main window if no arguments are provided.
 * For users whose workflow involves running Binary Ninja from a shell, just running `binaryninja` will try to activate a running instance, and if it does, return you to your shell. Otherwise it will launch a new instance of Binary Ninja.
 * Running `binaryninja` with a file path (or paths), like `binaryninja /bin/ls /bin/cat`, will 
-  1. Try to activate existing tabs for those files in a running instance, or failing that,   
+  1. Try to activate and focus existing tabs for those files in a running instance, or failing that,
   2. Try to open those files in new tabs in a running instance, or failing that,
   3. Open those files in a new instance of Binary Ninja.
-* Passing the `-n` or `--new-instance` command line argument will cause a new Binary Ninja application to be launched, and any files or URLs on the command line will be opened in the new instance.
+* Passing the `-n` or `--new-instance` command line argument will cause a new Binary Ninja application to be launched and any files or URLs on the command line will be opened in the new instance.
 
 ## Debugger
 
diff --git a/docs/guide/settings.md b/docs/guide/settings.md
index 75261836..50bbc335 100644
--- a/docs/guide/settings.md
+++ b/docs/guide/settings.md
@@ -344,7 +344,6 @@ All settings are uniquely identified with an identifier string. Identifiers are
 |ui.featureMap|Feature Map Location|Location of the feature map.|`string`|`right`|[`SettingsUserScope`]|<a id='ui.featureMap.location'>ui.featureMap.location</a>|
 | | |  enum: Feature map appears on the right side of the window.|`enum`|`right`| | |
 | | |  enum: Feature map appears at the top of the window.|`enum`|`top`| | |
-|ui.files|Always Open a New Instance from the Command Line|Force Binary Ninja to always open a new application instance when run from the command line with no arguments, instead of activating a running instance. If false, a new instance can always be opened using the '-n' command line argument.|`boolean`|`True`|[`SettingsUserScope`]|<a id='ui.files.commandLine.newInstance'>ui.files.commandLine.newInstance</a>|
 |ui.files|Existing Database Detection|When opening a file in the UI, detect if a database exists and offer to open the database.|`string`|`prompt`|[`SettingsUserScope`]|<a id='ui.files.detection.database'>ui.files.detection.database</a>|
 | | |  enum: Enable detection and generate prompt.|`enum`|`prompt`| | |
 | | |  enum: Enable detection and automatically open the file or database, if found.|`enum`|`always`| | |