Apply suggestions from code review

Co-authored-by: Nicolas Munnich <[email protected]>

docs/docs/troubleshooting/building-issues.md

@@ -68,7 +68,7 @@ A common mistake that leads to this error is to use [key press keycodes](keymaps
 If you want to ensure that the [configuration settings](../config/index.md#kconfig-files) you intend to change are changed in the build, you can check the final compiled Kconfig file that the firmware build process produces.
 This file will display values for all set configurations includes user, keyboard, ZMK and Zephyr-level settings.
 
-If using GitHub Actions to build your firmware, the contents of this file are displayed in the "<keyboard> Kconfig file" step in your build job:
+When using GitHub Actions to build your firmware, the contents of this file are displayed in the "<keyboard> Kconfig file" step in your build job:
 
 ![](../assets/troubleshooting/building/kconfig-step.png)
 
@@ -89,7 +89,7 @@ If you want to ensure that your [devicetree files](../config/index.md#devicetree
 This file will contain a single devicetree that is the result of all user, keyboard (board and/or shield) devicetree settings.
 Note that while it will include your keymap contents in it, [keycodes](../keymaps/list-of-keycodes.mdx) like `SPACE` will be displayed instead as hexadecimal numbers like `0x7002a`.
 
-If using GitHub Actions to build your firmware, the contents of this file are displayed in the "<keyboard> Devicetree file" step in your build job:
+When using GitHub Actions to build your firmware, the contents of this file are displayed in the "<keyboard> Devicetree file" step in your build job:
 
 ![](../assets/troubleshooting/building/devicetree-step.png)