fix typos

Author: MilagrosMarin

src/about/contribute.md

@@ -7,6 +7,7 @@ These guidelines are designed to ensure smooth collaboration, high-quality contr
 The principal maintainer of DataJoint and associated tools is the DataJoint company. The pronouns “we” and “us” in this guideline refer to the principal maintainers. We invite reviews and contributions of the open-source software. We compiled these guidelines to make this work clear and efficient.
 
 ## Table of Contents
+
 - [Community Engagement](#community-engagement)
 - [How to Contribute](#how-to-contribute)
   - [Project Lists](#project-lists)
@@ -18,7 +19,6 @@ The principal maintainer of DataJoint and associated tools is the DataJoint comp
 - [Releases](#releases)
 - [Contribution Acknowledgment](#contribution-acknowledgment)
 
-
 ## Community Engagement
 
 For general questions, ideas, discussions or live debugging sessions, please join [DataJoint Slack](https://join.slack.com/t/datajoint/shared_invite/enQtMjkwNjQxMjI5MDk0LTQ3ZjFiZmNmNGVkYWFkYjgwYjdhNTBlZTBmMWEyZDc2NzZlYTBjOTNmYzYwOWRmOGFmN2MyYzU0OWQ0MWZiYTE) or [Stack Overflow](https://stackoverflow.com/questions/tagged/datajoint), but for direct technical issues should stay in `Github Issue` in the respective project's repository. Response times may vary depending on maintainer availability.
@@ -40,7 +40,7 @@ Actively maintained projects by DataJoint:
 - [DataJoint Docs](https://github.com/datajoint/datajoint-docs)
   - It is the landing page of DataJoint documentation.
   - Each project has its own documentation in its repository.
-  - Please help us to improve our documetations, it's the easiest but most impactful way to contribute!
+  - Please help us to improve our documentations, it's the easiest but most impactful way to contribute!
 - [DataJoint Python](https://github.com/datajoint/datajoint-python)
 - [DataJoint Elements](https://github.com/orgs/datajoint/repositories?q=element)
 - [datajoint/djlabhub-docker](https://github.com/datajoint/djlabhub-docker)
@@ -91,7 +91,7 @@ Before starting your significant work, open a `Github Issue` to discuss your pro
     - Please remember to always sync your fork's main branch with the DataJoint repository's main branch before starting your work.
     - In your own fork, we suggest you use [Feature Branch Workflow](https://www.atlassian.com/git/tutorials/comparing-workflows/feature-branch-workflow) to manage your branches in your own fork, just in case someone will work on multiple contributions at the same time.
 2. Create a descriptive feature/fix branch from your fork's main branch, e.g., `fix/typo-docs` or `feature/add-logging`.
-3. Optionally, but highly recommended to follow [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) to make commit messages easier to be searched and categorized: If you use VSCode, please install [Conventional Commits](https://marketplace.visualstudio.com/items?itemName=vivaxy.vscode-conventional-commits) extention, it will help you to edit your commit messages following the commit types for versioning:
+3. Optionally, but highly recommended to follow [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) to make commit messages easier to be searched and categorized: If you use VSCode, please install [Conventional Commits](https://marketplace.visualstudio.com/items?itemName=vivaxy.vscode-conventional-commits) extension, it will help you to edit your commit messages following the commit types for versioning:
     - `fix`: Bug fixes.
     - `feat`: New features.
     - `docs`: Documentation updates.

src/elements/management/quality-assurance.md

@@ -22,7 +22,7 @@ When writing code, the following principles should be observed:
 
 - **Maintenance Overhead**: The size of the codebase should be considered to prevent
   unnecessarily large or complex solutions. As the codebase grows, the effort to review
-  and maintain it increases. Therefore, the goal is to find a balance that pevents the
+  and maintain it increases. Therefore, the goal is to find a balance that prevents the
   codebase from becoming too large while avoiding convoluted complexity.
 
 - **Performance**: Performance issues should be avoided, controlled, or, properly

src/projects/publications.md

@@ -12,7 +12,7 @@ The following publications relied on DataJoint open-source software for data ana
 
 ## 2024 
 
-+ Reimer, M. L., Kauer, S. D., Benson, C. A., King, J. F., Patwa, S., Feng, S., Estacion, M. A., Bangalore, L., Waxman, S. G., & Tan, A. M. (2024). [A FAIR, open-source virtual reality platform for dendritic spine analysis. Patterns](https://doi.org/10.1016/j.patter.2024.101041), 5(9). *Patterns*, 5(9).
++ Reimer, M. L., Kauer, S. D., Benson, C. A., King, J. F., Patwa, S., Feng, S., Estacion, M. A., Bangalore, L., Waxman, S. G., & Tan, A. M. (2024). [A FAIR, open-source virtual reality platform for dendritic spine analysis. Patterns](https://www.cell.com/patterns/pdf/S2666-3899(24)00183-1.pdf), 5(9). *Patterns*, 5(9).
 
 + Gillon, C. J., Baker, C., Ly, R., Balzani, E., Brunton, B. W., Schottdorf, M., Ghosh, S., & Dehghani, N. (2024). [Open Data In Neurophysiology: Advancements, Solutions & Challenges](https://doi.org/10.48550/arXiv.2407.00976). ArXiv, arXiv:2407.00976v1.