changes for JOSS publication (#363)

Author: danielskatz

joss-paper/paper.bib

@@ -1,8 +1,8 @@
 @article{Jolles:2021,
     url = {https://doi.org/10.1111/2041-210X.13652},
-    author  = {Jolle W.Jolles},
+    author  = {Jolle W. Jolles},
     journal = {Methods in Ecology and Evolution},
-    title   = {Broad‐scale applications of the Raspberry Pi: A Review and guide for Biologists.},
+    title   = {Broad‐scale applications of the {R}aspberry {P}i: A Review and guide for Biologists},
     year    = {2021},
     pages   = {1562-1579},
     volume  = {12},
@@ -15,7 +15,7 @@ @article{Longley:2017
     url = {https://doi.org/10.7717/peerj.2981},
     author  = {Longley M, Willis EL, Tay CX, Chen H},
     journal = {PeerJ},
-    title   = {An open source device for operant licking in rats.},
+    title   = {An open source device for operant licking in rats},
     year    = {2017},
     volume  = {5},
     doi     = {10.7717/peerj.2981}
@@ -24,7 +24,7 @@ @article{Longley:2017
 
 @article{Shah:2017,
     url = {http://dx.doi.org/10.26483/ijarcs.v8i9.4981},
-    author  = { Shah, Neel P., and Priyang Bhatt},
+    author  = {Shah, Neel P., and Priyang Bhatt},
     journal = {International Journal of Advanced Research in Computer Science},
     title   = {Greenhouse Automation and Monitoring System Design and Implementation},
     year    = {2017},
@@ -35,9 +35,9 @@ @article{Shah:2017
 
 @article{Knoll:2010,
     url = {https://doi.org/10.1002/cae.20217},
-    author  = { P. Knoll, S. Mirzaei},
+    author  = {P. Knoll, S. Mirzaei},
     journal = {Wiley Periodicals, Inc. Computions Applications in Engineering Education},
-    title   = {Scientific computing with Java},
+    title   = {Scientific computing with {J}ava},
     year    = {2010},
     pages   = {495–501},
     volume  = {18},
@@ -46,14 +46,14 @@ @article{Knoll:2010
 
 @software{RPi.GPIO,
     author = {Ben Croston},
-    title = {RPi.GPIO: A Python library for Raspberry Pi GPIO control},
+    title = {RPi.GPIO: A {P}ython library for {R}aspberry {P}i GPIO control},
     year = {2024},
     url = {https://pypi.org/project/RPi.GPIO/}
 }
 
 @software{Diozero,
     author = {Matt Hawkins},
-    title = {Diozero: Device I/O library for the Raspberry Pi and other platforms},
+    title = {Diozero: Device {I/O} library for the {R}aspberry {P}i and other platforms},
     year = {2024},
     url = {https://github.com/mattjlewis/diozero}
-}
+}

joss-paper/paper.md

@@ -52,7 +52,7 @@ promotes collaborative use in shared research environments, reducing the bottlen
 
 Existing software packages for Raspberry Pi GPIO control include **RPi.GPIO** [@RPi.GPIO], a popular Python library that provides direct, low-level access to GPIO pins and is widely used for simple hardware interfacing and scripting. However, RPi.GPIO is limited to Python and does not offer abstractions for hardware components or support for scalable application architectures. **Diozero** [@Diozero] provides a component-oriented Java API for GPIO, I2C, SPI, and PWM devices, encapsulating devices as high-level classes and supporting multiple board types.
 
-Both Diozero and Pi4Micronaut abstract hardware details, but Pi4Micronaut is mainly focused on Raspberry Pi and distinguished by its deep integration with the Micronaut framework, enabling advanced features such as dependency injection, modular microservice architectures, and seamless bean management. In Pi4Micronaut, hardware components are managed as Micronaut beans, enabling scalable and maintainable IoT applications for complex research and scientific computing.
+Both Diozero and Pi4Micronaut abstract hardware details, but Pi4Micronaut is mainly focused on Raspberry Pi and is distinguished by its deep integration with the Micronaut framework, enabling advanced features such as dependency injection, modular microservice architectures, and seamless bean management. In Pi4Micronaut, hardware components are managed as Micronaut beans, enabling scalable and maintainable IoT applications for complex research and scientific computing.
 
 Pi4Micronaut simplifies deployment by allowing developers to package the entire application as a single `.jar` file, reducing complexity and improving maintainability. 
 Additionally, this deployment model ensures that the entire application, including dependencies, is bundled in one executable file, simplifying installation and reducing the risk of version conflicts.