updates self hosted with Authentik device flow (#226)

* adds Authentik device flow

* corrects spelling issue and moves new section to better place

src/pages/how-to/google-workspace-sync.mdx

@@ -237,7 +237,7 @@ You can also click on `+ Add group (or user group) filter` to change this settin
 
 ![NetBird Users Sync](/docs-static/img/how-to-guides/google-workspace-sync/6Huo7vW.png)
 
-The next screen, should be similar the following one, verifying that the integration was succesful:
+The next screen, should be similar the following one, verifying that the integration was successful:
 
 ![NetBird Google Workspace Enabled](/docs-static/img/how-to-guides/google-workspace-sync/EkPJqpJ.png)
 

src/pages/how-to/okta-sync.mdx

@@ -166,7 +166,7 @@ Back to Okta, click `Edit` as shown below.
 Enable Okta to create, update, and deactivate NetBird users by checking the corresponding boxes:
 
 * Create Users
-* Update User Attibutes
+* Update User Attributes
 * Deactivate Users
 
 When done, click `Save`.
@@ -197,13 +197,13 @@ One more time, go to NetBird and click `Continue →`. You'll see the final inst
 ![NetBird Sync Groups to NetBird](/docs-static/img/how-to-guides/okta-sync/8TAvguS.png)
 
 * In Okta, navigate to `Push Groups` tab
-* Click the `Push Groups` buttom
+* Click the `Push Groups` button
 * Select `Find groups by name`
 * Search for specific groups to push to NetBird.
 
 ![XX](/docs-static/img/how-to-guides/okta-sync/uqUiTtg.png)
 
-Once you finish, go back to NetBird and click `Finish Setup`. You can verify the syncronization by navigating to `Team > Users`
+Once you finish, go back to NetBird and click `Finish Setup`. You can verify the synchronization by navigating to `Team > Users`
 
 ![XX](/docs-static/img/how-to-guides/okta-sync/GPTzvut.png)
 

src/pages/selfhosted/identity-providers.mdx

@@ -535,6 +535,19 @@ In this step, we will add `Netbird` service account to `authentik Admins` group.
     <img src="/docs-static/img/integrations/identity-providers/self-hosted/authentik-add-user-group.png" alt="high-level-dia" className="imagewrapper-big"/>
 </p>
 
+#### Step 5: Create a authentication flow for device token authentication
+Navigate to Authentik admin interface > Flows & Stages > Flows > Create
+<p>
+    <img src="/docs-static/img/integrations/identity-providers/self-hosted/authentik-new-device-flow.png" alt="high-level-dia" className="imagewrapper-big"/>
+</p>
+
+
+Then go to: System > Brands > Edit used default > Default Flows > set **Device code flow** to newly created device flow
+<p>
+    <img src="/docs-static/img/integrations/identity-providers/self-hosted/authentik-brand-device-flow.png" alt="high-level-dia" className="imagewrapper-big"/>
+</p>
+Press `Update`
+
 Your authority OIDC configuration will be available under:
 
 ```bash
@@ -561,7 +574,8 @@ NETBIRD_IDP_MGMT_EXTRA_USERNAME="Netbird"
 NETBIRD_IDP_MGMT_EXTRA_PASSWORD="<SERVICE_ACCOUNT_PASSWORD>"
 
 ```
-#### Step 5: Continue with the NetBird Self-hosting Guide
+
+#### Step 6: Continue with the NetBird Self-hosting Guide
 You've configured all required resources in Authentik. You can now continue with the [NetBird Self-hosting Guide](/selfhosted/selfhosted-guide#step-4-disable-single-account-mode-optional).
 
 ## Managed IDPs