Differences

This shows you the differences between two versions of the page.

--- getting_started:onboarding [2024/02/10 05:38] – system
+++ getting_started:onboarding [2024/02/10 05:45] (current) – system
@@ Line 4: / Line 4: @@
 </nav>
 ====== The purpose of new arrivals ======
-  * New arrivals are used to make on-boarding smoother.
+  * The purpose of new arrivals is to make onboarding smoother.
   * New arrivals are used in two places
         * RADIUS Clients
@@ Line 28: / Line 28: @@
 ===== Entries in New Arrivals =====
-  * Entries to New Arrivals are added **by the system**.
+  *  Entries in New arrivals are added **by the system**.
-  * When a RADIUS client which has not yet been added but who has the correct shared secret contacts the server (using the RADIUS protocol), it will be added to the New Arrivals for RADIUS under the RADIUS section.
+  * When a RADIUS client that has not yet been added but has the correct shared secret contacts the server (using the RADIUS protocol), it is added to the New arrivals for RADIUS under the RADIUS section.
-  * When hardware like a mesh node or AP with the MESHdesk firmware on, which is configured to point to the RADIUSdesk server contacts the server (using HTTP or HTTPS), and the hardware is not yet managed, it will be added to New Arrivals for Hardware under MESHdesk and APdesk.
+  *  If hardware such as a mesh node or an AP with the MESHdesk firmware configured to point to the RADIUSdesk server contacts the server (using HTTP or HTTPS) and the hardware is not yet managed, it will be added to the New arrivals for hardware under MESHdesk and APdesk.
 ===== Testing New Arrivals =====
-  * To confirm that the system add New Arrivals as intended you can test it by mimicking a RADIUS client and MESHdesk enabled hardware.
+  *  To confirm that the system is adding New Entrances as intended, you can test it by mimicking a RADIUS client and MESHdesk-enabled hardware.
-==== Mimic a RADIUS Client ====
+==== Imitating a RADIUS client ====
-  * RADIUSdesk has a built-in RADIUS client for your convenience.
+  * RADIUSdesk has a built-in RADIUS client that you can use conveniently.
-  * Under the **Overview** section is a **Utilities** tab with a **RADIUS Client** launch button.
+  * Under the Overview section, you will find a Utilities tab with a button to start the RADIUS client.
 <panel type="default" title="RADIUS Client">
 {{ :getting_started:radius_client_utiil.png|}}
@@ Line 46: / Line 46: @@
   * You can now either delete it, or attach it as a RADIUS Client.
-==== Mimic MESHdesk enabled hardware ====
+==== Imitate MESHdesk-capable hardware ====
-  * The MESHdesk enabled hardware will to a HTTP GET call to the RADIUSdesk server.
+  * The MESHdesk-enabled hardware performs an HTTP GET call to the RADIUSdesk server.
-  * This can be either using HTTP or HTTPS and is configurable.
+  *  This can be done either via HTTP or HTTPS and is configurable.
-  * The following can be used as a reference:
+  * The following URL can be used as a reference:
   * http://cloud.radiusdesk.com/cake4/rd_cake/nodes/get-config-for-node.json?gateway=true&_dc=1651070922&version=22.03&mac=00-3F-5D-00-8F-C5
   * The result when it is not yet managed will look like this
@@ Line 62: / Line 62: @@
 {{ :getting_started:meshdesk_new_arrival_result.png|}}
 </panel>
-  * You can now either delete it, or attach it as a node to a selected mesh network or AP to an AP Profile.
+  * You can now either delete it or attach it as a node to a selected mesh network or as an AP to an AP Profile.
 ==== New Arrivals - Devices ====
 <alert type="warning">
   * You may notice that there is also a New Arrivals button under Permanent Users.
-  * This is a work in progress and part of the PPSK solution which is still developed.
+  * This is still a work in progress and part of the PPSK solution that is still being developed.
 </alert>