Refine conclusion in README

Updated the conclusion section to enhance clarity and coherence.

Author: aluo13

README.md

@@ -183,21 +183,21 @@ Note: RFID recipe loading was removed from the final system design and is not in
 
 ### 4. Conclusion
 
-This project taught us a great deal about embedded system design, particularly the challenge of integrating mechanical, electrical, and software subsystems into a functioning real-time system. We learned that designing individual subsystems is often much easier than making them work together reliably, and that debugging integration issues can take significantly more time than expected. We also gained experience in practical topics such as sensor calibration, closed-loop control using feedback, MOSFET-based actuator driving, SPI peripheral integration, and power management for mixed-voltage systems.
+This project taught us a great deal about embedded system design, particularly the challenge of integrating mechanical, electrical, and software subsystems into a functioning system. We learned that designing individual subsystems is often much easier than making them work together reliably, and that debugging integration issues can take significantly more time than expected. 
 
 Several aspects of the project went well. One major success was our ability to adapt the specifications to better fit the realities of implementation, particularly pivoting from a linear slide architecture to a rotational dispensing platform, which simplified mechanical complexity while still satisfying the project goals. Our modular subsystem approach also worked well, allowing us to independently develop the touchscreen interface, pump-flow sensor control, and turntable mechanism before integrating them. We were also able to demonstrate a complete autonomous dispensing sequence, which was a major milestone.
 
-We are particularly proud of building a fully functioning automated drink dispensing prototype from the ground up and getting multiple subsystems—touchscreen UI, flow-controlled pumps, turntable positioning, and embedded control firmware—to operate together. We are also proud of working through several design pivots rather than forcing the original concept when it was no longer optimal. The project moved beyond a proof-of-concept into a true integrated electromechanical system.
+We are particularly proud of building a fully functioning automated drink dispensing prototype from the ground up and getting multiple subsystems, including a touchscreen UI, flow-controlled pumps, turntable positioning, and embedded control firmware, to operate together. We are also proud of working through several design pivots rather than forcing the original concept when it was no longer optimal. 
 
-From this experience, we gained a much stronger appreciation for system-level engineering and iterative prototyping. We learned that successful embedded design is often less about the first design being correct and more about rapidly identifying constraints, adjusting requirements, and improving the design through iteration. We also gained valuable experience with debugging at both the hardware and firmware level, especially in dealing with timing, calibration, and noisy real-world signals.
+From this experience, we learned that successful embedded system design is often less about the first design being correct and more about rapidly identifying constraints, adjusting requirements, and improving the design through iteration. We also gained valuable experience with debugging at both the hardware and firmware level. 
 
-We did have to change our approach several times. Early on, we realized integration introduced issues that were not obvious when testing subsystems independently, which forced us to redesign portions of both the mechanics and controls. We changed both the motion subsystem and parts of the sensing approach, and we shifted focus from adding features to prioritizing robustness of the core functionality.
+We definitely had to change our approach several times. Early on, we realized integration introduced issues that were not obvious when testing subsystems independently, which forced us to redesign portions of both the mechanics and controls. We changed both the motion subsystem and parts of the sensing approach, and we shifted focus from adding features to prioritizing robustness of the core functionality.
 
 In hindsight, some things could have been done differently. More time spent on subsystem interface planning and early integration testing would have likely reduced late-stage debugging. We also could have prioritized power architecture and driver thermal considerations much earlier, since these became significant bottlenecks later in the project. More extensive calibration testing earlier in development would also have improved dispensing accuracy.
 
 We did encounter obstacles we did not anticipate, especially around power management, which took significantly longer than expected. Managing multiple loads, protecting switching circuits, handling motor driver overheating, and ensuring stable operation under varying loads turned out to be much more challenging than initially assumed. Integration issues between mechanical motion and dispensing control also created challenges we had not fully predicted.
 
-A natural next step for this project would be improving calibration and dispensing accuracy so recipes can be reproduced more consistently. Additional work could include closed-loop control improvements, more robust motor driving hardware, and expanding the recipe system through RFID or another dynamic recipe-loading method. Beyond that, scaling to a more polished and reliable consumer-facing prototype with improved mechanical packaging and expanded drink customization would be an exciting continuation of the project.
+A potential next step for this project would be improving calibration and dispensing accuracy so recipes can be reproduced more consistently. Additional work could include closed-loop control improvements, more robust motor driving hardware, and expanding the recipe system through RFID or another dynamic recipe loading method. Beyond that, scaling to a more polished and reliable consumer-facing prototype with improved mechanical packaging and expanded drink customization would be an exciting continuation of the project.
 
 
 ## References