From 51d9ba3390e978aa633e535d988ce979a0b9d81f Mon Sep 17 00:00:00 2001 From: Bastian de Byl Date: Sat, 14 Oct 2023 16:45:34 -0400 Subject: [PATCH] noticket - markdownlint fixes --- content/post/bt_win_linux.md | 15 +++++++++------ content/post/headphone-fix.md | 2 +- content/post/password_checker.md | 2 +- content/post/stm32-part1.md | 2 +- content/post/updating_gpg_key.md | 2 +- 5 files changed, 13 insertions(+), 10 deletions(-) diff --git a/content/post/bt_win_linux.md b/content/post/bt_win_linux.md index 8505a65..ac51ded 100644 --- a/content/post/bt_win_linux.md +++ b/content/post/bt_win_linux.md @@ -14,11 +14,12 @@ This is a guide written on how to share the same Bluetooth device(s) across Wind 1. Pair your Bluetooth device(s) with Linux **first** 2. Reboot into Windows, then re-pair the devices with Windows 3. Run `regedit` **as Administrator** -4. Navigate to: - ``` +4. Navigate to: + + ```text HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BTHPORT\Parameters\Keys ``` - + If you **do not see any Keys under the tree** then you need to open `regedit` as a system-account user. One way to do this is using the PsExec by [downloading it from Microsoft Sysinternals](https://learn.microsoft.com/en-us/sysinternals/downloads/psexec). Once it is downloaded, you will need to run a command-prompt **as Administrator** and navigate to the location `PsExec` is unzipped and run `PsExec.exe -s -i regedit`. The Bluetooth keys should now be visible. 5. Right-click on `Keys` in the left-hand pane and select `Export`. During the dialog change `Save as type` to `Text files` and that the `Export range` is set to `Selected branch`. Store this somewhere **accessible by both Windows and Linux** -- if a shared drive is unavailable, use a USB drive or cloud-storage. @@ -28,10 +29,12 @@ This is a guide written on how to share the same Bluetooth device(s) across Wind 9. Open the `info` file, with root privileges, in the text editor of your choice. 10. In another tab/window, using either a text viewer or editor, open the **previously exported Windows registry text file for the device** 11. From the **Windows** file, copy the Bluetooth Key. Example: - ``` + + ```text 00000000 31 c0 08 fa 4f 7b d2 4c - 6f e1 7d ba 32 29 a9 a7 1À.ïO{ÒLoá}ºQ)©§ ``` + _From the above copy `31 c0 .... a9 a7`_ - + 12. Paste the key from the previous step into the `Key=` portion of the **Linux** Bluetooth `info` file. Make sure to **remove all spaces, hyphens, and change all characters to upper-case (all-caps)**. -13. Save the `info` file with the changes to complete device sharing. Repeat for any other Bluetooth devices to share. \ No newline at end of file +13. Save the `info` file with the changes to complete device sharing. Repeat for any other Bluetooth devices to share. diff --git a/content/post/headphone-fix.md b/content/post/headphone-fix.md index 332e8c0..cfbcce3 100644 --- a/content/post/headphone-fix.md +++ b/content/post/headphone-fix.md @@ -19,7 +19,7 @@ with the catch being: _I had to fix them_ Past mistakes have taught me to be gentle and patient when it comes to taking things apart. This was no exception either. After looking over the unit on each -side, I figured the only way *in* was lifting the mesh cover off. So I went at +side, I figured the only way _in_ was lifting the mesh cover off. So I went at it, carefully, with a pair of tweezers. I worked my way around the edge and wedged the mesh upwards. diff --git a/content/post/password_checker.md b/content/post/password_checker.md index bf13c75..3eb19ac 100644 --- a/content/post/password_checker.md +++ b/content/post/password_checker.md @@ -106,7 +106,7 @@ getpws() } ``` -This accomplishes our *first goal* of checking duplicate passwords -- +This accomplishes our _first goal_ of checking duplicate passwords -- **hooray!** # Passwortstärke diff --git a/content/post/stm32-part1.md b/content/post/stm32-part1.md index 04193e6..cffb3c1 100644 --- a/content/post/stm32-part1.md +++ b/content/post/stm32-part1.md @@ -109,7 +109,7 @@ For accomplishing this, a few things need to happen: {{< admonition warning "Note for Different STM32Fx Microcontrollers" >}} Review the datasheet for the specific **STM32Fx** microcontroller being -programmed, as the Alternate Function mappings may be *significantly* different! +programmed, as the Alternate Function mappings may be _significantly_ different! {{< /admonition >}} ## GPIO Alternate Function Setup diff --git a/content/post/updating_gpg_key.md b/content/post/updating_gpg_key.md index 297e1e8..edaea40 100644 --- a/content/post/updating_gpg_key.md +++ b/content/post/updating_gpg_key.md @@ -229,4 +229,4 @@ gpg --armor --export-secret-keys YOUREMAILADDRESS | gpg --armor --symmetric --ou Import it in OpenKeychain (_may require deletion in OpenKeychain first -- make sure **not to revoke and delete!**_) and we're done! -[^1]: https://guardianproject.info/archive/luks/ +[^1]: [guardianproject.info/archive/luks/](https://guardianproject.info/archive/luks/)