Whitespace changes

Klipper3d · Jan 1, 2024 · 3fa96e6 · 3fa96e6
1 parent 4b67c19
commit 3fa96e6
Show file tree

Hide file tree

Showing 11 changed files with 565 additions and 321 deletions.
diff --git a/config/printer-elegoo-neptune3-pro-2023.cfg b/config/printer-elegoo-neptune3-pro-2023.cfg
@@ -3,7 +3,7 @@
 # "32KiB bootloader" and serial (on USART1 PA10/PA9) communication.
 
 # For screen support, enable "Enable extra low-level configuration options"
-# and select "Enable serial bridge" and then "USART6" then uncommit the [neptune_screen] 
+# and select "Enable serial bridge" and then "USART6" then uncommit the [neptune_screen]
 # and serial_bridge sections
 
 

diff --git a/docs/Config_Reference.md b/docs/Config_Reference.md
@@ -4303,14 +4303,14 @@ information on menu attributes available during template rendering.
 
 ### [neptune screen]
 Support for the Elegoo screen for the Neptune 3/3 Plus/3 Max.
-A [serial bridge](#serial_bridge) must be setup for communciation to 
+A [serial bridge](#serial_bridge) must be setup for communciation to
 take place. Communication is based on versions (1.4.2) and earlier.
 
 ```
 [neptune_screen]
 #serial_bridge:
 #   Name of the serial_bridge to be used for communication
-#variant: 
+#variant:
 #   The device variant to report to the screen. Possible values are
 #   3Pro: Neptune 3 Pro
 #   3Max: Neptune 3 Max
@@ -4755,31 +4755,31 @@ via the `i2c_speed` parameter. All other Klipper micro-controllers use a
 ```
 
 ### [serial_bridge]
-Communication between the mcu and devices connected to its UART ports 
+Communication between the mcu and devices connected to its UART ports
 such as third-party screens can be bridged with this module. This feature
 must be enabled with the low-level configuration options when compiling the
-firmware specifying which ports should be available for the bridge to use. 
+firmware specifying which ports should be available for the bridge to use.
 Currently only STM32 devices are supported.
 
-See the [command reference](G-Codes.md#serial_bridge) for the different 
+See the [command reference](G-Codes.md#serial_bridge) for the different
 options and configurations available.
 
 ```
 [serial_bridge bridge_screen]
 #eol:
-#   The character or string of characters to be sent at the end of each 
+#   The character or string of characters to be sent at the end of each
 #   call. Defaults to \n
 #baud
 #   The baud rate for communication. Default is 115200
 #config:
-#   The serial configuration to use. These define the port and pins. 
+#   The serial configuration to use. These define the port and pins.
 #   List them  using the [command reference](G-Codes.md#serial_bridge)
 #   SERIAL_BRIDGE_LIST_CONFIGS
 #tx_pin:
-#   Pin used for Tx. This is used to reserve the pin and to look up 
+#   Pin used for Tx. This is used to reserve the pin and to look up
 #   the appropriate MCU
 #rx_pin
-#   Pin used for Rx. This is used to reserve the pin and to look up 
+#   Pin used for Rx. This is used to reserve the pin and to look up
 #   the appropriate MCU
 #logging
 #   Boolean to turn logging of or on for debugging communication

diff --git a/docs/G-Codes.md b/docs/G-Codes.md
@@ -1109,12 +1109,12 @@ has been enabled.
 send a serial message (TEXT) to the bridge specificed (BRIDGE).
 
 #### SERIAL_BRIDGE_LIST_CONFIGS
-`SERIAL_BRIDGE_LIST_CONFIGS`: This command will list the available 
+`SERIAL_BRIDGE_LIST_CONFIGS`: This command will list the available
 configurations reported by the MCU for use. This config should be used
 when setting up a new [serial_bridge](Config_Reference.md#serial_bridge).
 
 #### SERIAL_BRIDGE_LIST_BRIDGES
-`SERIAL_BRIDGE_LIST_BRIDGES`: This command will list the available 
+`SERIAL_BRIDGE_LIST_BRIDGES`: This command will list the available
 bridges ready for use from the printer configuration
 [serial_bridge](Config_Reference.md#serial_bridge).