docs: fix typos in developer docs and VM scripts - #16674
Conversation
|
Hey @vaibhav8a! 👋 Thank you for contributing to JabRef! We have automated checks in place, based on which you will soon get feedback if any of them are failing. We also use Qodo for review assistance. It will update your pull request description with a review help and offer suggestions to improve the pull request. After all automated checks pass, a maintainer will also review your contribution. Once that happens, you can go through their comments in the "Files changed" tab and act on them, or reply to the conversation if you have further inputs. You can read about the whole pull request process in our contribution guide. Please ensure that your pull request is in line with our AI Usage Policy and make necessary disclosures. |
PR Summary by QodoCorrect typos in developer and VM documentation
AI Description
High-Level Assessment
Files changed (5)
|
Code Review by Qodo🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)
Great, no issues found!Qodo reviewed your code and found no material issues that require reviewTip of the day💡 Did you know, you can hide the parts of a finding you never read, like the evidence or the agent prompt |
|
@vaibhav8a Since you removed the checklist, the license of your changes is unclear. Can you re-add the checklist or is this a one shot PR? |
|
I think it's fine. Just typo changes. |
|
You have removed the section "Checklist" from your pull request description. Please adhere to our pull request template. |
Six typo fixes across developer docs and scripts:
docs/code-howtos/faq.md:90commiting→committingdocs/code-howtos/openoffice/ooresult-ooerror/ooresult-alternatives.md:92,369exeption→exceptionjablib/src/test/resources/testbib/issue-12274/README.md:5Straight-foward→forwardscripts/vms/windows10/README.md:14destory→destroyscripts/vms/windows11/README.md:14destory→destroyDocumentation prose only — no code, test data, or Vagrant commands changed.