From 60c8ee88e57264c7c703bc9d2667e6592fe6c146 Mon Sep 17 00:00:00 2001
From: tominabox1 <tom.campie@gmail.com>
Date: Tue, 29 Dec 2020 09:02:21 -0600
Subject: [PATCH] fix tabs

---
 docs/docs/troubleshooting.md | 16 +++++++++-------
 1 file changed, 9 insertions(+), 7 deletions(-)

diff --git a/docs/docs/troubleshooting.md b/docs/docs/troubleshooting.md
index fc61ce3b..22f5212d 100644
--- a/docs/docs/troubleshooting.md
+++ b/docs/docs/troubleshooting.md
@@ -2,6 +2,8 @@
 title: Troubleshooting
 sidebar_title: Troubleshooting
 ---
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
 
 ### Summary
 
@@ -91,10 +93,10 @@ The workaround for this limitation is as follows:
 1. Now open the terminal app (Applications/Utilities/Terminal.app) and paste the following command and enter your root password. 
 
    <Tabs
-      defaultValue="HS"
-      values={[
-      {label: 'macOS High Sierra (10.13) and newer', value: 'high_sierra'},
-      {label: 'macOS Sierra (10.12) and older', value: 'sierra'},
+   defaultValue="high_sierra"
+   values={[
+   {label: 'macOS High Sierra 10.13 and newer', value: 'high_sierra'},
+   {label: 'macOS Sierra 10.12 and older', value: 'sierra'},
    ]}>
    <TabItem value="high_sierra"> 
 
@@ -108,7 +110,7 @@ The workaround for this limitation is as follows:
    ```
    sudo defaults read /private/var/root/Library/Preferences/blued.plist
    ```
-   
+
    </TabItem>
    </Tabs>
 
@@ -118,7 +120,7 @@ The workaround for this limitation is as follows:
    | :------------------------------------------------------------: |
    |                         Bluetooth .plist                       |
  
- 1. Look for the section that starts with `SMPDistributionKeys =`. Below this, find your host's bluetooth address (`65-FD-3B-1A-DB-48` in this example) and then look for the address of your keyboard (`6E-24-54-08-BC-A3` in this example).
+ 1. Look for the section that starts with `SMPDistributionKeys =`. Below this, find your host's bluetooth address (`65-FD-3B-1A-DB-48` in this example) and then look for the address of your keyboard (`E6-24-54-08-BC-A3` in this example).
  1. Under your keyboard address, find the value labeled LocalLTK (in the screenshot above it is `0x8968239e350b2cb7df16d8f47c774e2c`). Copy this value into a text file that you can access from Windows, this is the value we will need to enter into the registry later on.
  1. Reboot into Windows
  1. Once logged in, turn off bluetooth. 
@@ -140,7 +142,7 @@ The workaround for this limitation is as follows:
    ```
 
 1. Inside "Keys", select the address of your host bluetooth device. It should be the same as it was in macOS (`65-FD-3B-1A-DB-48` in this example).
-1. Below that, find the address that matches your keyboard's from macOS (`6E-24-54-08-BC-A3` in this example).
+1. Below that, find the address that matches your keyboard's from macOS (`E6-24-54-08-BC-A3` in this example).
 
    | ![Registry Key](../docs/assets/troubleshooting/dualboot/Registry1.png) |
    | :--------------------------------------------------------------------: |