diff --git a/README.md b/README.md
index 2969acc..48b4af3 100644
--- a/README.md
+++ b/README.md
@@ -6,11 +6,11 @@ description: Telecom Infra Project Open Wi-Fi
## What is Open Wi-Fi?
-TIP Open Wi-Fi is an open source community project that believes in democratizing premium Wi-Fi experiences for multiple market use cases. The TIP approach to Open Wi-Fi creates an open source disaggregated technology stack without any vendor lock in. Open Wi-Fi offers premium managed Wi-Fi features, local break-out design, cloud native open source controller, and an open source AP firmware operating system tested nightly.
+TIP Open Wi-Fi is an open source community project that believes in democratizing premium Wi-Fi experiences for multiple market use cases. The TIP approach to Open Wi-Fi creates an open source disaggregated technology stack without any vendor lock in. Open Wi-Fi offers premium managed Wi-Fi features, local break-out design, cloud native open source controller, and an open source AP firmware operating system tested nightly.
-TIP Open Wi-Fi is the industry's first CI/CD open source Wi-Fi eco-system. Built nightly with a strong community of Wi-Fi leaders, new features are unit tested in automated RF chambers and checked from cloud to ground for Wi-Fi performance and conformance.
+TIP Open Wi-Fi is the industry's first CI/CD open source Wi-Fi eco-system. Built nightly with a strong community of Wi-Fi leaders, new features are unit tested in automated RF chambers and checked from cloud to ground for Wi-Fi performance and conformance.
### High Level Features
@@ -31,7 +31,6 @@ TIP Open Wi-Fi is the industry's first CI/CD open source Wi-Fi eco-system. Built
* Template based device provisioning with RADIUS profile management
* Advanced RF control with RRM
-
**Open Wi-Fi AP Detail List:**
* IEEE 802.11b/g/n/ac/ax
@@ -120,5 +119,5 @@ TIP Open Wi-Fi is the industry's first CI/CD open source Wi-Fi eco-system. Built
### **How to contribute**
-If you or your company are interested in contributing to TIP Open Wi-Fi, please join the Wi-Fi Product Group by visiting [Telecom Infra Project](https://telecominfraproject.com/apply-for-membership/) to become a member.
+If you or your company are interested in contributing to TIP Open Wi-Fi, please join the Wi-Fi Product Group by visiting [Telecom Infra Project](https://telecominfraproject.com/apply-for-membership/) to become a member.
diff --git a/api/README.md b/api/README.md
index d6f44e2..f8f3da3 100644
--- a/api/README.md
+++ b/api/README.md
@@ -1,18 +1,18 @@
# API
-TIP Open Wi-Fi project is a data-model driven design, meaning the features in the solution are designed as interfaces to be consumed either by micro-services, network devices, or other applications integrating with the solution.
+TIP Open Wi-Fi project is a data-model driven design, meaning the features in the solution are designed as interfaces to be consumed either by micro-services, network devices, or other applications integrating with the solution.
-The most useful way to learn the TIP Open Wi-Fi API is to consume the Swagger interface that fully describes all implemented REST methods.
+The most useful way to learn the TIP Open Wi-Fi API is to consume the Swagger interface that fully describes all implemented REST methods.
-TIP Open Wi-Fi controller uses OAuth for authentication. A bearer token must first be obtained for subsequent API calls to succeed.
+TIP Open Wi-Fi controller uses OAuth for authentication. A bearer token must first be obtained for subsequent API calls to succeed.
-### Curl Request to controller for Bearer Token
+## Curl Request to controller for Bearer Token
```text
curl -k --request POST --header "Content-Type: application/json; charset=utf-8" --data '{"userId":"support@example.com","password":"support"}' https://${portal-service-ip:port}/management/v1/oauth2/token
```
-### Successful Response
+## Successful Response
```text
{
diff --git a/api/swagger.md b/api/swagger.md
index c7839b6..83e7bbd 100644
--- a/api/swagger.md
+++ b/api/swagger.md
@@ -4,25 +4,25 @@ description: Online and Local Open API Access
# Open API
-TIP Open Wi-Fi controller implements an Open API compliant NorthBound Interface \(NBI\) to assist with integration and related back office features.
+TIP Open Wi-Fi controller implements an Open API compliant NorthBound Interface \(NBI\) to assist with integration and related back office features.
-Cloud SDK north bound API is a key function for most open source community members or vendors seeking to consume the SDK for integration or for value added software development above the SDK layer.
+Cloud SDK north bound API is a key function for most open source community members or vendors seeking to consume the SDK for integration or for value added software development above the SDK layer.
+
+Swagger is a useful tool to explore and learn any system API. Both online and local options are available to help development teams consume the Cloud SDK.
-Swagger is a useful tool to explore and learn any system API. Both online and local options are available to help development teams consume the Cloud SDK.
-
Running a local Swagger instance requires a current version of NodeJS installed.
-### Online Swagger - Cloud SDK Open API
+## Online Swagger - Cloud SDK Open API
-Current SDK open API is available at the following URL: [CloudSDK Open API](https://l.workplace.com/l.php?u=https%3A%2F%2Fapi.lab.wlan.tip.build%2F&h=AT2qj4RJnFaxruxpxP2s8O-XjRQMEbCC7aoVbHaHxmOxgfOgi5LHv6lWdCU4aV8x2vJcsxGmY-UKxb8W86xaDH-VtVLomBcBkdEHVxlpssluOoSPiIMC-vXU0NtGW44qktgKDJc934Dl2kr0QnRyZw)
+Current SDK open API is available at the following URL: [CloudSDK Open API](https://l.workplace.com/l.php?u=https%3A%2F%2Fapi.lab.wlan.tip.build%2F&h=AT2qj4RJnFaxruxpxP2s8O-XjRQMEbCC7aoVbHaHxmOxgfOgi5LHv6lWdCU4aV8x2vJcsxGmY-UKxb8W86xaDH-VtVLomBcBkdEHVxlpssluOoSPiIMC-vXU0NtGW44qktgKDJc934Dl2kr0QnRyZw)
-### Local Swagger - Obtain latest Cloud SDK Open API Model
+## Local Swagger - Obtain latest Cloud SDK Open API Model
When running a local instance of Swagger, first obtain the most current Cloud SDK open API from source control:
{% embed url="https://github.com/Telecominfraproject/wlan-cloud-services/blob/master/portal-services/src/main/resources/portal-services-openapi.yaml" caption="TIP Github repo link to Open API data model " %}
-#### Install Swagger
+### Install Swagger
```text
mkdir ~/swagger
@@ -36,9 +36,7 @@ npm run build
npm start
```
-With Swagger running, open the Open API data model file and begin to use locally on port 9091 or add your own TIP Open Wi-Fi controller to the Swagger definitions. Remember to obtain an [OAuth bearer ](./#curl-request-to-controller-for-bearer-token)token to 'Authorize' your session.
+With Swagger running, open the Open API data model file and begin to use locally on port 9091 or add your own TIP Open Wi-Fi controller to the Swagger definitions. Remember to obtain an [OAuth bearer ](./#curl-request-to-controller-for-bearer-token)token to 'Authorize' your session.
-
-
diff --git a/configuration-examples/basic-device-provisioning.md b/configuration-examples/basic-device-provisioning.md
index 92f1272..907b8ae 100644
--- a/configuration-examples/basic-device-provisioning.md
+++ b/configuration-examples/basic-device-provisioning.md
@@ -4,7 +4,7 @@ description: Cloud SDK Profile Use
# Basic Device Provisioning
-Cloud SDK processes Profiles by aggregating certain profile types as child profiles inherited during device configuration.
+Cloud SDK processes Profiles by aggregating certain profile types as child profiles inherited during device configuration.
@@ -33,30 +33,24 @@ Cloud SDK processes Profiles by aggregating certain profile types as child profi
-Association of devices to Access Point and SSID is possible as one-to-one \(1:1\) or one-to-many \(1:M\).
-The decision on using 1:1 or 1:M is entirely based on the desired deployment.
+Association of devices to Access Point and SSID is possible as one-to-one \(1:1\) or one-to-many \(1:M\).
+The decision on using 1:1 or 1:M is entirely based on the desired deployment.
-Creating a 1:1 Access Point Profile could be useful in certain lab or specific network locations. If a specific RF Profile was desired on a select device, using an Access Point Profile with reference to the specific RF Profile would accomplish this provisioning logic.
+Creating a 1:1 Access Point Profile could be useful in certain lab or specific network locations. If a specific RF Profile was desired on a select device, using an Access Point Profile with reference to the specific RF Profile would accomplish this provisioning logic.
-Creating an RF Profile specifically for IEEE802.11ac Wi-Fi 5 Access Points to inherit may be a common approach with another RF Profile for all IEEE802.11ax Wi-Fi 6 Access Points. Another reason to create a unique RF Profile may configured outdoor RF configuration that is unique from other indoor based Access Points.
+Creating an RF Profile specifically for IEEE802.11ac Wi-Fi 5 Access Points to inherit may be a common approach with another RF Profile for all IEEE802.11ax Wi-Fi 6 Access Points. Another reason to create a unique RF Profile may configured outdoor RF configuration that is unique from other indoor based Access Points.
-Creating RF Profile with specific Client Steering, Channel Hop, or general radio operation other than default settings are useful when defining behavior of Access Points individually or as a large group of managed devices.
+Creating RF Profile with specific Client Steering, Channel Hop, or general radio operation other than default settings are useful when defining behavior of Access Points individually or as a large group of managed devices.
-#### Wi-Fi 5 802.11AC Mode General RF Profile
+## Wi-Fi 5 802.11AC Mode General RF Profile
Example Wi-Fi 5 IEEE802.11AC RF Profile:
-#### Wi-Fi 6 802.11AX Mode General RF Profile
+## Wi-Fi 6 802.11AX Mode General RF Profile
Example Wi-Fi 6 IEEE802.11AX RF Profile
-
-
-
-
-
-
diff --git a/getting-started/README.md b/getting-started/README.md
index bf65162..bb4c7ea 100644
--- a/getting-started/README.md
+++ b/getting-started/README.md
@@ -1,7 +1,7 @@
# Getting Started
-Deploying the TIP Open Wi-Fi solution into a lab or into production is simple to do.
-Some basic pre-requisites should be satisfied before beginning.
+Deploying the TIP Open Wi-Fi solution into a lab or into production is simple to do.
+Some basic pre-requisites should be satisfied before beginning.
Ensure the following are known before beginning installation:
diff --git a/getting-started/controller-installation/README.md b/getting-started/controller-installation/README.md
index 71505fe..351c48b 100644
--- a/getting-started/controller-installation/README.md
+++ b/getting-started/controller-installation/README.md
@@ -1,16 +1,12 @@
# Cloud SDK Installation
-Open Wi-Fi Cloud SDK may be deployed to both public and private cloud environments.
+Open Wi-Fi Cloud SDK may be deployed to both public and private cloud environments.
-Helm charts support automated deployment of the Cloud SDK PODs and containers into AWS and MicroK8s Kubernetes platforms.
+Helm charts support automated deployment of the Cloud SDK PODs and containers into AWS and MicroK8s Kubernetes platforms.
-The following pages provide step-by-step instructions to deploy in public cloud \(AWS\) or private on-premises \(MicroK8s\) cloud.
+The following pages provide step-by-step instructions to deploy in public cloud \(AWS\) or private on-premises \(MicroK8s\) cloud.
{% page-ref page="aws-install.md" %}
{% page-ref page="microk8s-install.md" %}
-
-
-
-
diff --git a/getting-started/controller-installation/aws-install.md b/getting-started/controller-installation/aws-install.md
index efebc07..337c4b7 100644
--- a/getting-started/controller-installation/aws-install.md
+++ b/getting-started/controller-installation/aws-install.md
@@ -22,16 +22,16 @@ Each of these applications provide detailed instructions for installation on mul
### Example Local Prerequisites Installation on MAC OS
- If the instructions for Terraform were followed, a Docker container was locally created, nginx was run with a default localhost:80 nginx returned web page displayed. After which 'terraform destroy' was run to remove the local test of Terraform.
+If the instructions for Terraform were followed, a Docker container was locally created, nginx was run with a default localhost:80 nginx returned web page displayed. After which 'terraform destroy' was run to remove the local test of Terraform.
-If the instructions for AWS CLI were followed, AWS CLI version 2 has been installed. This may be verified using the command `which aws` and `aws --version`. If these succeed installation of AWS CLI has completed.
+If the instructions for AWS CLI were followed, AWS CLI version 2 has been installed. This may be verified using the command `which aws` and `aws --version`. If these succeed installation of AWS CLI has completed.
If the instructions for Helm were followed, Helm has now been locally installed. This may be verified using the command `which helm` and `helm version`. If these succeed installation of Helm has completed.
If the instructions for Kubectl were followed, Kubectl has not been locally installed. This may be verified using the command which `kubectl` and `kubectl version --client`. If these succeed installation of Kubectl has completed.
{% hint style="info" %}
- If any of the above have not completed, please refer back to the specific install instructions from the package provider listed in the Prerequisite links accordingly before continuing.
+If any of the above have not completed, please refer back to the specific install instructions from the package provider listed in the Prerequisite links accordingly before continuing.
{% endhint %}
Access to AWS should have been satisfied with an AWS account as noted in Prerequisites. This account is entitled with Administrator level permissions. For information on this process please refer to: [https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-quickstart.html](https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-quickstart.html)
@@ -48,7 +48,7 @@ git checkout cloudsdk-aws-deployment
cd /terraform/aws-cloudsdk
```
- Create a Terraform file in the `aws-cloudsdk` directory named `aws.tf`adding the following to that new file:
+Create a Terraform file in the `aws-cloudsdk` directory named `aws.tf`adding the following to that new file:
```text
provider "aws" {
@@ -58,9 +58,9 @@ provider "aws" {
If a specific authentication method previously exists depending on your local machine environment when connecting to AWS, adjustments may be required. Please consult Terraform instructions accordingly: [https://registry.terraform.io/providers/hashicorp/aws/latest/docs\#authentication](https://registry.terraform.io/providers/hashicorp/aws/latest/docs#authentication)
-### Initialize Terraform
+### Initialize Terraform
-Terraform will use the initial configuration of your environment variables from the previous step when communicating with AWS. Prior to initializing Terraform, ensure authentication is successful.
+Terraform will use the initial configuration of your environment variables from the previous step when communicating with AWS. Prior to initializing Terraform, ensure authentication is successful.
```text
terraform init
@@ -73,7 +73,7 @@ Terraform has been successfully initialized!
### Adjusting to AWS Environment
-Within the `/wlan-cloud-helm/terraform/aws-cloudsdk` directory, copy the `terraform.tfvars.sample` file to `terraform.tfvars` and edit the content of the new `terraform.tfvars` replacing parameter values for cidr and route53\_zone\_name accordingly:
+Within the `/wlan-cloud-helm/terraform/aws-cloudsdk` directory, copy the `terraform.tfvars.sample` file to `terraform.tfvars` and edit the content of the new `terraform.tfvars` replacing parameter values for cidr and route53\_zone\_name accordingly:
```text
name = "cloudsdk"
@@ -82,7 +82,7 @@ route53_zone_name = "Enter a valid Route53 Hosted-Zone"
subdomain = "cloudsdk"
```
-Once these steps have been completed, it is now possible to deploy the TIP Controller to AWS.
+Once these steps have been completed, it is now possible to deploy the TIP Controller to AWS.
```text
terraform apply
@@ -103,7 +103,7 @@ If Terraform is able to connect and authenticate to AWS, a prompt to accept the
When Terraform completes the following should have emitted:
> **Apply complete! Resources: 57 added, 0 changed, 0 destroyed.**
-
+>
> **Outputs:**
>
> **acm\_arn = "arn:aws:acm:ca-central-1:1**_**xxxxxxx**_**68:certificate/7e3**_**xxxx**_**7-74**_**xx**_**-4**_**xxx**_**-8bef-d6**_**xxxxxx**_**5a3"**
@@ -122,15 +122,15 @@ Modify all certificate configuration files for the value of your organizationalU
Within the following files, ensure the FQDN \(Fully Qualified Domain Name\) based on the Terraform setup for Route53 hosted-zone aligns accordingly. If the defaults were not changed Terraform will have created a sub-domain `cloudsdk` within the supplied Route53 hosted-zone. The following files are updated per:
-* mqtt-server.cnf
+* mqtt-server.cnf
- `commonName_default = opensync-mqtt-broker.cloudsdk.route53hosted-zone_name`
+ `commonName_default = opensync-mqtt-broker.cloudsdk.route53hosted-zone_name`
-* openssl-server.cnf
+* openssl-server.cnf
- `DNS.1 = opensync-redirector.cloudsdk.route53hosted-zone_name`
+ `DNS.1 = opensync-redirector.cloudsdk.route53hosted-zone_name`
- `DNS.2 = opensync-controller.cloudsdk.route53hosted-zone_name`
+ `DNS.2 = opensync-controller.cloudsdk.route53hosted-zone_name`
To generate keys, ensure necessary Java resources are installed for your operating system:
@@ -142,7 +142,7 @@ From within the `wlan-pki-cert-scripts` folder execute `./generate_all.sh` scrip
Copy the generated keys assuming the wlan-cloud-helm folder is at the same level as the wlan-pki-certs folder per: `./copy-certs-to-helm.sh ~/wlan-cloud-helm/`
{% hint style="info" %}
-`Note within the wlan-pki-cert-scripts folder, a subfolder /generated is present after key creation.`
+`Note within the wlan-pki-cert-scripts folder, a subfolder /generated is present after key creation.`
`The AP.zip archive in the generated folder contains the Access Point certificates for loading onto APs in the AP /usr/opensync/certs device folder`
{% endhint %}
@@ -157,9 +157,11 @@ helm dependency update tip-wlan
Various Bitnami charts will be brought into the deployment such as Kafka, PostGres, Cassandra.
-Localizing the Helm charts for AWS is a critical step. Editing the following file
+Localizing the Helm charts for AWS is a critical step. Editing the following file
- `tip-wlan/example-values/aws-basic/values.yml`
+```text
+ `tip-wlan/example-values/aws-basic/values.yml`
+```
**Key variables to replace in this file are:**
@@ -175,7 +177,7 @@ Localizing the Helm charts for AWS is a critical step. Editing the following fil
Local Kubeconfig is associated to the AWS service to enable Helm control of EKS resources by entering the following:
```text
-aws eks update-kubeconfig --region $your_aws_region --name cloudsdk
+aws eks update-kubeconfig --region $your_aws_region --name cloudsdk
```
With all dependencies met, certificates created and in place, using Helm and the authenticated session to AWS, execute the following:
@@ -189,10 +191,10 @@ If a connection error occurs, AWS CLI may need to re-authenticate. This can be d
If Helm has a successful connection to AWS the following returns:
> Release "cloudsdk" does not exist. Installing it now.
-
+>
> NAME: cloudsdk
>
-> LAST DEPLOYED: Sun Feb 7 14:00:28 2021
+> LAST DEPLOYED: Sun Feb 7 14:00:28 2021
>
> NAMESPACE: tip
>
@@ -221,7 +223,6 @@ cloudsdk-wlan-prov-service-944f44d67-4p5z5 0/1 PodInit
cloudsdk-wlan-spc-service-596ff5c546-bmgw5 0/1 Init:0/1 0 100s
cloudsdk-wlan-ssc-service-6db4c8c8b8-jrmrc 0/1 Init:0/2 0 100s
cloudsdk-zookeeper-0 1/1 Running 0 99s
-
```
After 5 to 8 minutes elapse, all POD services should be operational for example:
@@ -247,7 +248,7 @@ cloudsdk-zookeeper-0 1/1 Running
### Check in on the UI
-Navigate to https://wlan-ui.cloudsdk.yourdomainname
+Navigate to [https://wlan-ui.cloudsdk.yourdomainname](https://wlan-ui.cloudsdk.yourdomainname)
diff --git a/getting-started/controller.md b/getting-started/controller.md
index d27ab97..e96f155 100644
--- a/getting-started/controller.md
+++ b/getting-started/controller.md
@@ -4,20 +4,17 @@ description: TIP Open Wi-Fi
# Cloud SDK
-With the Cloud SDK now installed into either a public cloud or on premises, logging in with default username **support@example.com** and password **support** are now possible.
+With the Cloud SDK now installed into either a public cloud or on premises, logging in with default username **support@example.com** and password **support** are now possible.
-Once successfully logged in, please refer to [User Interface](../user-interface/) documentation for further details of specific configuration.
+Once successfully logged in, please refer to [User Interface](../user-interface/) documentation for further details of specific configuration.
{% hint style="info" %}
Current TIP Cloud SDK deploys using self-signed certificates. This requires accepting the self-signed certificate in the UI for the following URLs:
- https://wlan-ui.wlan.local
- https://wlan-ui-graphql.wlan.local
+[https://wlan-ui.wlan.local](https://wlan-ui.wlan.local)
+[https://wlan-ui-graphql.wlan.local](https://wlan-ui-graphql.wlan.local)
Navigate to both URLs and accept the certificate exception.
-Once the client browser has these certificate exceptions loaded login will succeed.
+Once the client browser has these certificate exceptions loaded login will succeed.
{% endhint %}
-
-
-
diff --git a/mdu-quick-start/solution-overview/supported-configuration.md b/mdu-quick-start/solution-overview/supported-configuration.md
index 5aab7ef..326320e 100644
--- a/mdu-quick-start/solution-overview/supported-configuration.md
+++ b/mdu-quick-start/solution-overview/supported-configuration.md
@@ -1,8 +1,6 @@
# Supported Configuration
-Multiple Dwelling Units \(MDU\) are a common style of Wi-Fi deployment. For our Supported Configuration in the MDU Quick Start, we propose a sample 2 story building with 10 apartments per floor total 20 units for the building.
-
-Deployment of access point devices in this example use common areas such as hallways, gym, lobby areas.
-
+Multiple Dwelling Units \(MDU\) are a common style of Wi-Fi deployment. For our Supported Configuration in the MDU Quick Start, we propose a sample 2 story building with 10 apartments per floor total 20 units for the building.
+Deployment of access point devices in this example use common areas such as hallways, gym, lobby areas.
diff --git a/ordering-open-wi-fi-aps.md b/ordering-open-wi-fi-aps.md
index dd8a746..59bb79e 100644
--- a/ordering-open-wi-fi-aps.md
+++ b/ordering-open-wi-fi-aps.md
@@ -4,9 +4,7 @@ description: TIP Wi-Fi Member Access Point Ordering Information
# Ordering Open Wi-Fi APs
-TIP Wi-Fi members may contact the ODM manufacturers in the TIP Wi-Fi eco-system using the information posted within Community Confluence page.
-
-{% embed url="https://telecominfraproject.atlassian.net/wiki/spaces/WIFI/pages/112689187/AP+Hardware" %}
-
+TIP Wi-Fi members may contact the ODM manufacturers in the TIP Wi-Fi eco-system using the information posted within Community Confluence page.
+{% embed url="https://telecominfraproject.atlassian.net/wiki/spaces/WIFI/pages/112689187/AP+Hardware" caption="" %}
diff --git a/user-interface/README.md b/user-interface/README.md
index 1174c22..04f6e28 100644
--- a/user-interface/README.md
+++ b/user-interface/README.md
@@ -6,13 +6,13 @@ description: TIP Cloud SDK
## Navigating the UI
-TIP open source SDK offers a web based user interface supporting many common configurations. The web based interface uses the SDK north bound API.
-
-It is possible to further extend functionality of the SDK user interface or to create other interfaces using the SDK API.
+TIP open source SDK offers a web based user interface supporting many common configurations. The web based interface uses the SDK north bound API.
-### Log In
+It is possible to further extend functionality of the SDK user interface or to create other interfaces using the SDK API.
-Default user account is `support@example.com` with password `support`.
+### Log In
+
+Default user account is `support@example.com` with password `support`.
If using the self-signed certificates provided in the open source distribution, it will be necessary to add an exception to the web browser for the following URLs:
@@ -21,7 +21,5 @@ If using the self-signed certificates provided in the open source distribution,
Further instructions available [here](../getting-started/controller.md).
-
-
diff --git a/user-interface/accounts.md b/user-interface/accounts.md
index 4b6806a..468a532 100644
--- a/user-interface/accounts.md
+++ b/user-interface/accounts.md
@@ -4,11 +4,11 @@ description: Cloud SDK Accounts
# Accounts
-Cloud SDK local accounts support user interface and API connections. Adding and removing accounts from the web user interface may be completed from the Users navigation tab.
+Cloud SDK local accounts support user interface and API connections. Adding and removing accounts from the web user interface may be completed from the Users navigation tab.
-Select `'Add User'` to create a new Cloud SDK user, assign a Role and password.
+Select `'Add User'` to create a new Cloud SDK user, assign a Role and password.
diff --git a/user-interface/dashboard.md b/user-interface/dashboard.md
index 76a3e41..3eb921b 100644
--- a/user-interface/dashboard.md
+++ b/user-interface/dashboard.md
@@ -8,15 +8,15 @@ TIP Cloud SDK is organized into main components presented along the top of the s
-Dashboard is the default landing page for the user interface.
-Network enables management of Access Points and display of Client Devices status.
-Profiles enables template based management of all provisioning parameters.
-System enables Manufacturer OUI Updates, Firmware Updates, Auto-Provisioning and Client Block List.
+Dashboard is the default landing page for the user interface.
+Network enables management of Access Points and display of Client Devices status.
+Profiles enables template based management of all provisioning parameters.
+System enables Manufacturer OUI Updates, Firmware Updates, Auto-Provisioning and Client Block List.
Users enables configuration of local user accounts of the Cloud SDK.
-Alarm indicates an error condition has occurred with one or multiple Access Points.
-Gear icon to Log Out.
+Alarm indicates an error condition has occurred with one or multiple Access Points.
+Gear icon to Log Out.
-### Dashboard Components
+## Dashboard Components
@@ -72,5 +72,3 @@ Gear icon to Log Out.
-
-
diff --git a/user-interface/network.md b/user-interface/network.md
index 6acd819..f8b404d 100644
--- a/user-interface/network.md
+++ b/user-interface/network.md
@@ -4,56 +4,52 @@ description: Manage Devices and Monitor Clients
# Network
-From the Network page it is possible to create organizational regions to group devices within, view all devices, retrieve individual device records and view all associated and disassociated client devices.
+From the Network page it is possible to create organizational regions to group devices within, view all devices, retrieve individual device records and view all associated and disassociated client devices.
-### Location Tree
+## Location Tree
-In a future release it will be possible to assign devices to new locations to help in building an administrative hierarchy supporting convenient organization of device to service location. This functionality is exposed in the API and may be further refined in subsequent open source UI releases.
+In a future release it will be possible to assign devices to new locations to help in building an administrative hierarchy supporting convenient organization of device to service location. This functionality is exposed in the API and may be further refined in subsequent open source UI releases.
-### Access Points
+## Access Points
-For each access point that has contacted Cloud SDK, a row will populate within Access Points.
-Specific information for each device including Device name, alarm state, model and IP address are shown.
+For each access point that has contacted Cloud SDK, a row will populate within Access Points.
+Specific information for each device including Device name, alarm state, model and IP address are shown.
-Along the right side of each Access Point row are Profile, Channel, Occupancy, Noise Floor and Devices.
-Channel indicates the current provisioned RF Channel for each radio in the device.
-Occupancy indicates available RF bandwidth for Wi-Fi clients as a value over 100.
-Noise Floor represents the reported RF noise condition being measured by the device within the operating channel and reported to the Cloud SDK.
-Devices indicated the total associated clients for each radio in the access point.
+Along the right side of each Access Point row are Profile, Channel, Occupancy, Noise Floor and Devices.
+Channel indicates the current provisioned RF Channel for each radio in the device.
+Occupancy indicates available RF bandwidth for Wi-Fi clients as a value over 100.
+Noise Floor represents the reported RF noise condition being measured by the device within the operating channel and reported to the Cloud SDK.
+Devices indicated the total associated clients for each radio in the access point.
-#### Access Point Device Record
+### Access Point Device Record
Each access point managed by Cloud SDK inherits provisioning information from Profiles in addition to supporting device specific configurations and reporting device specific operating conditions.
-General information includes device name, model, MAC address and country of operation.
+General information includes device name, model, MAC address and country of operation.
Status presents operating conditions for each frequency band of operation in addition to Alarms.
Location permits the assignment of the device to a location in Cloud SDK hierarchy tree.
-#### OS Stats
+### OS Stats
-Operating System Stats are sent to Cloud SDK from each device using the MQTT interface. These statistics are regularly received as part of the overall telemetry stream.
+Operating System Stats are sent to Cloud SDK from each device using the MQTT interface. These statistics are regularly received as part of the overall telemetry stream.
-#### Firmware
+### Firmware
-The Cloud SDK may initiate an on demand firmware upgrade for any associated device. The Active Version of firmware is reported to the Cloud SDK. If the reported version from the device is not part of the System known firmware, the status will be `'UNDEFINED'`.
+The Cloud SDK may initiate an on demand firmware upgrade for any associated device. The Active Version of firmware is reported to the Cloud SDK. If the reported version from the device is not part of the System known firmware, the status will be `'UNDEFINED'`.
-Several TIP devices implement a secondary boot loader bank which Cloud SDK supports the method to command a device to `'Switch to Inactive Bank and Reboot'` .
+Several TIP devices implement a secondary boot loader bank which Cloud SDK supports the method to command a device to `'Switch to Inactive Bank and Reboot'` .
-To initiate a firmware upgrade, select a version from the drop down within Upgrade, select the `'Download, Flash, Reboot'` button.
+To initiate a firmware upgrade, select a version from the drop down within Upgrade, select the `'Download, Flash, Reboot'` button.
-#### On-Demand Device Reboot
+### On-Demand Device Reboot
-Within the Firmware sub-tab, Reboot AP button. Selecting this will cause Cloud SDK to send a warm reboot command to the Access Point.
-
-
-
-
+Within the Firmware sub-tab, Reboot AP button. Selecting this will cause Cloud SDK to send a warm reboot command to the Access Point.
diff --git a/user-interface/profiles.md b/user-interface/profiles.md
index 9806d20..bd988c4 100644
--- a/user-interface/profiles.md
+++ b/user-interface/profiles.md
@@ -4,21 +4,21 @@ description: Configuration Templates
# Profiles
-Cloud SDK uses multiple templates to perform provisioning of Cloud SDK managed devices.
+Cloud SDK uses multiple templates to perform provisioning of Cloud SDK managed devices.
-Sample default templates are provided on initial startup of Cloud SDK.
+Sample default templates are provided on initial startup of Cloud SDK.
-### Templates
+## Templates
| Type | Role |
| :--- | :--- |
| RF | Radio Frequency configuration parameters |
-| SSID | Service Set Identifier |
+| SSID | Service Set Identifier |
| RADIUS | Authentication Authorization Accounting Configuration per SSID |
| Equipment AP | 1:1 or 1:Many Device Association to RF Profile and SSID |
-| Captive Portal | Access Point Captive Portal configuration parameters |
+| Captive Portal | Access Point Captive Portal configuration parameters |
| Passpoint | R1 & R2 Compliant IEEE 802.11u configuration parameters |
| Passpoint ID Provider | R2 Compliant Offload, Venue, NAI and OpenRoaming configuration parameters |