Update README.md

spectral-cockpit · Sep 11, 2023 · 337a2d4 · 337a2d4
1 parent fb90561
commit 337a2d4
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/README.md b/README.md
@@ -20,7 +20,7 @@ the company Bruker Optics GmbH & Co. in R. This package is being developed in ou
 
 The [Bruker corporation](https://www.bruker.com/en.html) manufactures reliable instruments but there is no official documentation of the OPUS file format. Hence the format is proprietary. Luckily, we and our colleagues from the open source spectroscopy community have cracked it. With some heavy lifting we have unscrambled the file logic (see credits).
 
-{opusreader2} is a state-of-the-art binary reader. We recommend the package as a solid foundation for your spectroscopy workflow. It is modular and has no hard dependencies apart from base R. By providing feedback, opening and solving issues, or making pull requests, you can actively contribute to the spectroscopy communities. These efforts are mainly to support more and more instruments, measurement modes, and block types. You can also soon rely on our ready-made diagnostic solutions building upon it. If you wish, the [spectral-cockpit team](https://github.com/spectral-cockpit) further offers consulting service along your entire spectroscopy workflow. 
+{opusreader2} is a state-of-the-art binary reader. We recommend the package as a solid foundation for your spectroscopy workflow. It is modular and has no hard dependencies apart from base R. By providing feedback, opening and solving issues, or making pull requests, you can actively contribute to the spectroscopy communities. These efforts are mainly to support more and more instruments, measurement modes, and block types. You can also soon rely on our ready-made diagnostic solutions building upon it. If you wish, the [spectral-cockpit.space team](https://github.com/spectral-cockpit) further offers consulting service along your entire spectroscopy workflow. 
 
 We have reached stable package development now. The core API of `opusreader2::read_opus()` is solid and we are not planning any major user-facing design changes. There will be extended capabilities after basic reading in additional functions downstream. For example, to exact specific parts of interest like measurement metadata or to accomplish read workflows for custom environments.