diff --git a/Hardware/Design Choices.markdown b/Hardware/Design Choices.markdown
index 2983b25..d93bca7 100644
--- a/Hardware/Design Choices.markdown	
+++ b/Hardware/Design Choices.markdown	
@@ -25,19 +25,21 @@ The board is going to be organized to the best of our abilities to be organized
     - CANbus Controller 1 (Microchip Technology MCP2515T-I/SO)
   - A1:
   - A2 [UART]:
-    - RS-232 Transceiver (STMicroelectronics ST232CDR)
-  - A3 [UART]:
     - USB to UART Bridge (Future Technology Devices International FT230XS-R)
+  - A3 [UART]:
+    - RS-232 Transceiver (STMicroelectronics ST232CDR)
+
 - B - Supporting up to four total of I2C and/or SPI
   - B0 [SPI]:
     - SD Card
     - GPS Receiver (Maxim Integrated ‎MAX2771ETI+T)
-  - B1 [SPI]:
-    - Bluetooth/Wi-Fi (Espressif Systems ESP32-WROVER-IE (8MB))
-  - B2 [I2C]:
+  - B1 [I2C]:
     - Inertial Measurement Unit (TDK InvenSense ICM-20600)
     - Real-Time Clock/Calendar (Microchip Technology ‎MCP7940MT-I/SN)
+  - B2:
+  - B3 [SPI]:
+    - Bluetooth/Wi-Fi (Espressif Systems ESP32-WROVER-IE (8MB))
 
 
 
-The thinking behind this so far, is to try and balance the load between the modules with SPI protocol being used in more high data-rate peripherals and I2C used with lower or less-used peripherals. In Texas Instruments SLAS655G Document [Page 7] has a pin diagram showing the physical location of where each pin is physically located.
\ No newline at end of file
+In addition to trying to keep the MCU and PCB organized with the left-side being to do with the Sunseeker vehicle and the right side to be peripherals interacting with users, we tried to also load-balance the USCI modules, as well as have the SPI protocol be used in more high data-rate peripherals and I2C used with lower or less-used peripherals. In Texas Instruments SLAS655G Document [Page 7] has a pin diagram showing the physical location of where each pin is physically located.
\ No newline at end of file