diff --git a/docs/administration/role-based-access-control/index.mdx b/docs/administration/role-based-access-control/index.mdx
index 0ad80fbdd..192ca6e26 100644
--- a/docs/administration/role-based-access-control/index.mdx
+++ b/docs/administration/role-based-access-control/index.mdx
@@ -155,24 +155,25 @@ As with Object Categories, it's not necessary to assign a subnet category to eve
 
 ## Assigning Object Permissions to Admin Groups
 
-Object permissions apply to the following objects: 
+You can assign admin groups to objects from the list view of the object type or the edit page of a specific object. You can also assign admin groups to discovered objects.
+
+The **Add Groups** and **Delete Groups** actions are available for the following objects: 
+
 - Buildings 
 - Rooms 
 - Racks 
-- Devices 
-- Assets 
-- Object Categories 
-- PDUs 
-- VRF Groups 
-- Subnet Categories 
-- Purchases
-- Vendors 
 - Customers 
-- Auto Discovery jobs
-
-You can assign admin groups to objects from the list view of the object type or the edit page of a specific object. You can also assign admin groups to discovered objects.
-
-From the list view of the object type, you can bulk select the objects you want to assign permissions to. From the **Actions** dropdown, select the **Assign Permissions** action.
+- Discovery job objects:
+  - AD/LDAP Sync 
+  - Certificate Autodiscovery 
+  - Cloud Autodiscovery
+  - Hypervisors/*nix/win for Autodiscovery
+  - IPMI/Redfish Autodiscovery
+  - Ping Sweep
+  - SNMP Autodiscovery
+  - UCS/ACI/Load Balancers for Autodiscovery
+
+From the list view of the object type, bulk select the objects you want to assign permissions to. From the **Actions** dropdown, select the **Add Groups** action.
 
 <ThemedImage
   alt="Add Groups action"
@@ -196,14 +197,6 @@ Remove previously assigned permissions with the **Delete Groups** action. If you
 
 You can also assign permissions from object edit pages, as shown above.
 
-The **Add Groups** and **Delete Groups** actions are available for the following objects: 
-- Buildings 
-- Rooms 
-- Racks 
-- VRF Groups
-
-Similarly, the device, asset, and PDU list pages have **Set Object Category** and **Delete Object Category** actions. The Subnet list page has **Set Subnet Category** and **Delete Subnet Category** actions.
-
 ## Who Can Assign Admin Groups to Objects?
 
 Superusers are allowed to add, change, and delete groups for objects through the UI, import spreadsheets, or the API. Superusers can also enable non-superusers to have this ability by assigning them add, change, and delete capabilities for "Object Permissions".
diff --git a/docs/auto-discovery/index.mdx b/docs/auto-discovery/index.mdx
index adbd0906a..c5d24362a 100644
--- a/docs/auto-discovery/index.mdx
+++ b/docs/auto-discovery/index.mdx
@@ -230,15 +230,6 @@ The Device42 remote collector (RC) is a lightweight virtual appliance (a VM) tha
 
 For more information head to the dedicated [Remote Collector page](auto-discovery/remote-collector-rc.mdx).
 
-## Scripts for Linux, Solaris, Windows, and Mac
-
-There is a selection of open-source scripts on the Device42 GitHub page: 
-
-- For Mac, Linux, and Solaris autodiscovery, see the [`nix_bsd_mac_inventory`](https://github.com/device42/nix_bsd_mac_inventory) repository.
-- Windows discovery scripts can be found on the [Device42 GitHub repository](https://github.com/device42). 
-
-Windows scripts use PowerShell 2.0/iPython to get individual Windows host details and to get Windows machines. Details are relayed to the Device42 Main Appliance via the API. The Linux, Solaris, and Mac scripts connect to remote servers using SSH to gather inventory data, sending that data back via the Device42 RESTful API.
-
 ## Using REST APIs
 
 You can automate inventory management and integrate with your own scripts or other programs using the Device42 RESTful APIs as shown in the [Create Hardware Models](how-to-videos/api-imports-add-create-hardware-models.mdx) video.
diff --git a/docs/getstarted/installation/discovery-port-configurations.mdx b/docs/getstarted/installation/discovery-port-configurations.mdx
index bdc5ea311..266ee1533 100644
--- a/docs/getstarted/installation/discovery-port-configurations.mdx
+++ b/docs/getstarted/installation/discovery-port-configurations.mdx
@@ -8,6 +8,7 @@ Below is a complete reference list of all ports that may be used to access targe
 | Source                        | Default Port       | Protocol  | Directionality | Reason                                     |
 |-------------------------------|--------------------|-----------|----------------|---------------------------------------------|
 | Main Appliance (MA)           | 389 (TCP/UDP)<br/>636 (TCP/UDP)      | LDAP<br/>LDAPS      | MA to targets  | Active Directory Sync                      |
+| Main Appliance (MA)           | 123 (UDP)          | NTP       | MA to targets  | Time synchronization                       |
 | Remote Collector(s) (RC)      | 53 (TCP)           | DNS       | Device42 to targets | DNS Zone Discovery                 |
 | Remote Collector(s) (RC)      | 623 (UDP)          | IPMI      | RC to targets  | IPMI based discovery of management interfaces |
 | Remote Collector(s) (RC)      | 22 (TCP)           | SSH       | RC to targets  | SSH based discovery of Linux and Unix systems |