updates for 2.6 release

integrations file fix
added correct path in toc
minor edits "TIP OpenWiFi"

SUMMARY.md

@@ -7,7 +7,7 @@
 * [About OpenWifi](about/about-openwifi.md)
 * [Open WiFi First](about/contribute.md)
 * [Supported Hardware](about/supported-hardware.md)
-* [Integrations](openwifi-stack/openwifi-stack.md)
+* [Integrations](about/integrations.md)
 * [Device Partner Information](about/device-partner-information.md)
 * [Cloud Partner Information](about/cloud-partner-information.md)
 * [Ordering OpenWiFi APs](about/ordering-open-wi-fi-aps.md)

about/about-openwifi.md

@@ -1,6 +1,6 @@
-# About OpenWifi
+# About TIP OpenWifi
 
-## About TIP OpenWifi
+## Moving OpenWifi. Further.
 
 Meta Connectivity provides solutions leveraging the Telecom Infra Project (TIP) OpenWiFi ecosystem—as part of the TIP Open Converged Wireless Project Group.
 

getting-started/access-points.md

@@ -35,9 +35,8 @@ It is possible to apply a firmware update from the Maverick interface. This oper
 
 ![Maverick based firmware upgrade](../.gitbook/assets/image%20%289%29.png)
 
-Manually setting the cloud location may be done using its Fully Qualified Domain Name \(FQDN\) in the Redirector field. Device certificates are unique per TIP Open WiFi access point or switch. It should not be required to change these values at any time. Please exercise caution if replacing certificates manually. 
+Manually setting the cloud location may be done using its Fully Qualified Domain Name \(FQDN\) in the Redirector field. Device certificates are unique per TIP OpenWiFi access point or switch. It should not be required to change these values at any time. Please exercise caution if replacing certificates manually. 
 
 ![Maverick set Cloud 'Redirector'](../.gitbook/assets/image%20%2817%29.png)
 
 ###
-