[Vale.Spelling] Did you really mean 'Jentery'?

[Vale.Spelling] Did you really mean 'minimal_computing_intro_image'?

[Google.LyHyphens] 'publicly-accessible' doesn't need a hyphen.

[Vale.Spelling] Did you really mean 'Heritrix'?

[Vale.Spelling] Did you really mean '_sass'?

[Vale.Spelling] Did you really mean 'repo'?

[Vale.Spelling] Did you really mean 'componenet'?

[Vale.Spelling] Did you really mean 'DOIs'?

[Vale.Spelling] Did you really mean 'DOIs'?

[Vale.Spelling] Did you really mean 'Zenodo'?

[Vale.Spelling] Did you really mean 'Zenodo'?

[Vale.Spelling] Did you really mean 'Zenodo'?

[Vale.Spelling] Did you really mean 'Zenodo'?

[Vale.Spelling] Did you really mean 'Zenodo'?

[Vale.Spelling] Did you really mean 'Zenodo'?

[Vale.Spelling] Did you really mean 'Zenodo'?

[Vale.Spelling] Did you really mean 'Zenodo'?

[Vale.Spelling] Did you really mean 'Zenodo'?

[Vale.Spelling] Did you really mean 'Zenodo'?

[Vale.Spelling] Did you really mean 'DOIs'?

[Vale.Spelling] Did you really mean 'DOIs'?

[Vale.Spelling] Did you really mean 'DOIs'?

[Vale.Spelling] Did you really mean 'DOIs'?

[Vale.Spelling] Did you really mean 'Zenodo'?

[Google.Quotes] Commas and periods go inside quotation marks.

[Google.Quotes] Commas and periods go inside quotation marks.

[Google.Quotes] Commas and periods go inside quotation marks.

[Vale.Spelling] Did you really mean 'access_jekyll_site'?

[Vale.Spelling] Did you really mean 'locate_theme'?

[Vale.Spelling] Did you really mean 'invoke_explorer'?

[Vale.Spelling] Did you really mean 'updatable'?

[Vale.Spelling] Did you really mean 'DOIs'?

[Vale.Spelling] Did you really mean 'citability'?

[Vale.Spelling] Did you really mean 'accessor'?

[Vale.Spelling] Did you really mean 'inaccessabile'?

[Vale.Spelling] Did you really mean 'unavailabe'?

[Vale.Spelling] Did you really mean 'DOIs'?

[Vale.Spelling] Did you really mean 'Immproving'?

[Vale.Spelling] Did you really mean 'Neuroimaging'?

[Vale.Spelling] Did you really mean 'DOIs'?

[Vale.Spelling] Did you really mean 'findability'?

[Vale.Spelling] Did you really mean 'DOIs'?

[Vale.Spelling] Did you really mean 'ciability'?

[Vale.Spelling] Did you really mean 'DOIs'?

[Vale.Spelling] Did you really mean 'DOIs'?

[Vale.Spelling] Did you really mean 'DOIs'?

[Vale.Spelling] Did you really mean 'DOIs'?

[Vale.Spelling] Did you really mean 'funders'?

[Vale.Spelling] Did you really mean 'DOIs'?

[Vale.Spelling] Did you really mean 'infrastracture'?

[Vale.Spelling] Did you really mean 'DOIs'?

[Vale.Spelling] Did you really mean 'DOIs'?

[Vale.Spelling] Did you really mean 'DOIs'?

[Vale.Spelling] Did you really mean 'Zenodo'?

[Vale.Spelling] Did you really mean 'eScience'?

[Vale.Spelling] Did you really mean 'Navbar'?

[Vale.Spelling] Did you really mean 'navbar'?

[Vale.Spelling] Did you really mean 'navbar'?

[Vale.Spelling] Did you really mean 'navbar'?

[Vale.Spelling] Did you really mean 'navbar'?

[Vale.Spelling] Did you really mean 'navbar'?

[Vale.Spelling] Did you really mean 'navbar'?

[Vale.Spelling] Did you really mean 'Navbar'?

[Vale.Spelling] Did you really mean 'bundler'?

[Vale.Spelling] Did you really mean 'Bundler'?

[Vale.Spelling] Did you really mean 'baseurl'?

[Vale.Spelling] Did you really mean 'url'?

[Vale.Spelling] Did you really mean 'hostname'?

[Vale.Spelling] Did you really mean 'Atlassian'?

[Vale.Spelling] Did you really mean 'Jira'?

[Google.Quotes] Commas and periods go inside quotation marks.

[Vale.Spelling] Did you really mean 'degredation'?

[Vale.Spelling] Did you really mean 'obselescence'?

[Vale.Spelling] Did you really mean 'Zenodo'?

[Vale.Spelling] Did you really mean 'Findability'?

[Vale.Spelling] Did you really mean 'DOIs'?

[Vale.Spelling] Did you really mean 'findability'?

[Vale.Repetition] 'the' is repeated!

[Vale.Spelling] Did you really mean 'inclusivity'?

[Vale.Spelling] Did you really mean 'reusability'?

[Vale.Spelling] Did you really mean 'modifiability'?

[Vale.Spelling] Did you really mean 'APIs'?

[Vale.Spelling] Did you really mean 'Haudenosaunee'?

[Vale.Spelling] Did you really mean 'Haudenosaunee'?

[Vale.Spelling] Did you really mean 'Ligne'?

[Vale.Spelling] Did you really mean 'eScience'?

[Vale.Spelling] Did you really mean 'funders'?

[Vale.Spelling] Did you really mean 'reproducibiltiy'?

[Vale.Spelling] Did you really mean 'signifcance'?

[Vale.Spelling] Did you really mean 'Hejazi'?

[Vale.Spelling] Did you really mean 'findability'?

[Vale.Spelling] Did you really mean 'reusability'?

[Vale.Spelling] Did you really mean 'Findability'?

[Vale.Spelling] Did you really mean 'Findability'?

[Vale.Spelling] Did you really mean 'PIDs'?

[Vale.Spelling] Did you really mean 'DOIs'?

[Vale.Spelling] Did you really mean 'PIDs'?

[Vale.Spelling] Did you really mean 'DOIs'?

[Vale.Spelling] Did you really mean 'Reusability'?

[Vale.Spelling] Did you really mean 'Reusability'?

[Vale.Spelling] Did you really mean 'impactful'?

[Vale.Spelling] Did you really mean 'invovles'?

[Vale.Spelling] Did you really mean 'developement'?

[Vale.Spelling] Did you really mean 'documention'?

[Vale.Spelling] Did you really mean 'middleware'?

[Vale.Spelling] Did you really mean 'iWork'?

[Vale.Spelling] Did you really mean 'photographics'?

[Vale.Spelling] Did you really mean 'Zenodo'?

[Vale.Spelling] Did you really mean 'eScience'?

[Vale.Spelling] Did you really mean 'findability'?

[Vale.Spelling] Did you really mean 'Zenodo'?

[write-good.TooWordy] 'It is' is too wordy.

[write-good.TooWordy] 'type of' is too wordy.

[write-good.TooWordy] 'However' is too wordy.

[write-good.Passive] 'is assigned' may be passive voice. Use active voice if you can.

[Google.Headings] 'Research Software and Research Impact' should use sentence-style capitalization.

[Google.OxfordComma] Use the Oxford comma in 'Open scholarship, also known as open science, refers to the movement towards making research and scholarly work openly accessible, transparent and'.

[Google.OxfordComma] Use the Oxford comma in 'Open scholarship encompasses principles and practices aimed at promoting collaboration, transparency and'.

[write-good.Weasel] 'various' is a weasel word!

[write-good.TooWordy] 'It is' is too wordy.

[Google.OxfordComma] Use the Oxford comma in 'Open-source software is software where the source code is freely available, allowing others to view, modify and'.

[write-good.TooWordy] 'modify' is too wordy.

[Google.WordList] Use 'open source' instead of 'open-source'.

[Google.We] Try to avoid using first-person plural like 'we'.

[Google.We] Try to avoid using first-person plural like 'our'.

[Google.We] Try to avoid using first-person plural like 'We'.

[Google.Headings] 'Further Readings' should use sentence-style capitalization.

[Google.Headings] 'Minimal Computing' should use sentence-style capitalization.

[Google.OxfordComma] Use the Oxford comma in 'Throughout this learning module, you will explore the principles and practices of minimal computing, a methodology focused on simplicity, accessibility and'.

[Google.Will] Avoid using 'will'.

[write-good.TooWordy] 'methodology' is too wordy.

[Google.We] Try to avoid using first-person plural like 'We'.

[Google.Will] Avoid using 'will'.

[write-good.TooWordy] 'demonstrate' is too wordy.

[Google.We] Try to avoid using first-person plural like 'we'.

[Google.WordList] Use 'style sheet' instead of 'stylesheet'.

[Google.We] Try to avoid using first-person plural like 'we'.

[Google.WordList] Use 'style sheet' instead of 'stylesheet'.

[write-good.TooWordy] 'modify' is too wordy.

[Google.WordList] Use 'style sheet' instead of 'stylesheet'.

[Google.WordList] Use 'style sheet' instead of 'stylesheet'.

[Google.WordList] Use 'style sheet' instead of 'stylesheet'.

[Google.Will] Avoid using 'will'.

[Google.We] Try to avoid using first-person plural like 'we'.

[Google.Will] Avoid using 'will'.

[Google.WordList] Use 'style sheet' instead of 'stylesheet'.

[write-good.Passive] 'be added' may be passive voice. Use active voice if you can.

[Google.WordList] Use 'style sheet' instead of 'stylesheet'.

[Google.Will] Avoid using 'will'.

[write-good.Passive] 'be asked' may be passive voice. Use active voice if you can.

[write-good.Passive] 'been created' may be passive voice. Use active voice if you can.

[Google.Will] Avoid using 'will'.

[write-good.Passive] 'be used' may be passive voice. Use active voice if you can.

[Google.Will] Avoid using 'will'.

[Google.Headings] 'Building Your Researcher Portfolio with ORCID ID' should use sentence-style capitalization.

[Google.We] Try to avoid using first-person plural like 'we'.

[Google.Will] Avoid using 'will'.

[Google.Headings] 'Generate DOI for Your Research Software' should use sentence-style capitalization.

[write-good.TooWordy] 'It is' is too wordy.

[Google.Will] Avoid using 'will'.

[Google.Will] Avoid using 'will'.

[Google.Will] Avoid using 'will'.

[write-good.Passive] 'is marked' may be passive voice. Use active voice if you can.

[Google.Will] Avoid using 'will'.

[write-good.TooWordy] 'subsequent' is too wordy.

[Google.Will] Avoid using 'will'.

[write-good.Passive] 'be created' may be passive voice. Use active voice if you can.

[Google.Will] Avoid using 'will'.

[write-good.Passive] 'is desired' may be passive voice. Use active voice if you can.

[Google.Will] Avoid using 'will'.

[Google.Headings] 'Adding Your Research Software to Your ORCID ID Record' should use sentence-style capitalization.

[write-good.TooWordy] 'it is' is too wordy.

[Google.Will] Avoid using 'will'.

[Google.Headings] 'A. Understand theme structure' should use sentence-style capitalization.

[write-good.Passive] 'are used' may be passive voice. Use active voice if you can.

[Google.Headings] 'B. Override theme defaults' should use sentence-style capitalization.

[write-good.TooWordy] 'However' is too wordy.

[write-good.TooWordy] 'modify' is too wordy.

[Google.We] Try to avoid using first-person plural like 'we'.

[Google.Will] Avoid using 'will'.

[Google.Will] Avoid using 'will'.

[write-good.Passive] 'be provided' may be passive voice. Use active voice if you can.

[write-good.Weasel] 'various' is a weasel word!

[write-good.Passive] 'is provided' may be passive voice. Use active voice if you can.

[write-good.Passive] 'is provided' may be passive voice. Use active voice if you can.

[Google.WordList] Use 'style sheet' instead of 'stylesheet'.

[Google.Headings] 'Digital Object Identifier (DOI)' should use sentence-style capitalization.

[Google.OxfordComma] Use the Oxford comma in 'They serve as stable and permanent identifiers for digital content, enabling reliable linking, referencing and'.

[Google.Will] Avoid using 'will'.

[write-good.Passive] 'is associated' may be passive voice. Use active voice if you can.

[Google.OxfordComma] Use the Oxford comma in 'The use of DOIs has become a standard practice in scholarly publishing and other digital content distribution platforms, promoting the permanence, reliability and'.

[write-good.TooWordy] 'utilization' is too wordy.

[Google.Headings] 'DOI and Research Software' should use sentence-style capitalization.

[write-good.Passive] 'be cited' may be passive voice. Use active voice if you can.

[write-good.Passive] 'be referenced' may be passive voice. Use active voice if you can.

[write-good.Passive] 'being used' may be passive voice. Use active voice if you can.

[write-good.Passive] 'is designed' may be passive voice. Use active voice if you can.

[write-good.Passive] 'be compared' may be passive voice. Use active voice if you can.

[Google.OxfordComma] Use the Oxford comma in 'Many funding agencies, journals and'.

[write-good.Passive] 'be assigned' may be passive voice. Use active voice if you can.

[write-good.TooWordy] 'requirement' is too wordy.

[write-good.TooWordy] 'as to' is too wordy.

[write-good.TooWordy] 'multiple' is too wordy.

[write-good.Passive] 'be created' may be passive voice. Use active voice if you can.

[write-good.Passive] 'be created' may be passive voice. Use active voice if you can.

[Google.Will] Avoid using 'will'.

[write-good.Passive] 'be presented' may be passive voice. Use active voice if you can.

[Google.OxfordComma] Use the Oxford comma in 'DOIs are widely recognized and integrated into academic databases, libraries and'.

[write-good.Passive] 'be found' may be passive voice. Use active voice if you can.

[write-good.TooWordy] 'modify' is too wordy.

[Google.We] Try to avoid using first-person plural like 'our'.

[Google.We] Try to avoid using first-person plural like 'we'.

[write-good.TooWordy] 'utilize' is too wordy.

[Google.We] Try to avoid using first-person plural like 'we'.

[write-good.Passive] 'is provided' may be passive voice. Use active voice if you can.

[write-good.Passive] 'is provided' may be passive voice. Use active voice if you can.

[write-good.Passive] 'is provided' may be passive voice. Use active voice if you can.

[Google.WordList] Use 'style sheet' instead of 'stylesheet'.

[Google.WordList] Use 'style sheet' instead of 'stylesheet'.

[Google.Headings] 'Create a File Named **************** in ***** folder' should use sentence-style capitalization.

[write-good.Passive] 'is provided' may be passive voice. Use active voice if you can.

[Google.Headings] 'Create a File Named *********** in ********* folder' should use sentence-style capitalization.

[write-good.Passive] 'is provided' may be passive voice. Use active voice if you can.

[Google.Headings] 'Add custom Stylesheet for the Navbar' should use sentence-style capitalization.

[Google.WordList] Use 'style sheet' instead of 'stylesheet'.

[Google.We] Try to avoid using first-person plural like 'we'.

[Google.Will] Avoid using 'will'.

[Google.We] Try to avoid using first-person plural like 'we'.

[Google.Will] Avoid using 'will'.

[Google.WordList] Use 'style sheet' instead of 'stylesheet'.

[write-good.Passive] 'be added' may be passive voice. Use active voice if you can.

[Google.WordList] Use 'style sheet' instead of 'stylesheet'.

[write-good.TooWordy] 'type of' is too wordy.

[Google.OxfordComma] Use the Oxford comma in 'With modern web browsers, HTML5 and'.

[write-good.Passive] 'be removed' may be passive voice. Use active voice if you can.

[Google.WordList] Use 'open source' instead of 'open-source'.

[Google.We] Try to avoid using first-person plural like 'We'.

[Google.Will] Avoid using 'will'.

[Google.WordList] Use 'open source' instead of 'open-source'.

[write-good.Passive] 'is built' may be passive voice. Use active voice if you can.

[write-good.TooWordy] 'It is' is too wordy.

[write-good.Passive] 'are stored' may be passive voice. Use active voice if you can.

[write-good.TooWordy] 'all of' is too wordy.

[Google.Will] Avoid using 'will'.

[write-good.Passive] 'be read' may be passive voice. Use active voice if you can.

[write-good.TooWordy] 'In the case of' is too wordy.

[write-good.Passive] 'are used' may be passive voice. Use active voice if you can.

[write-good.TooWordy] 'as to' is too wordy.

[Google.Will] Avoid using 'will'.

[write-good.Passive] 'be pulled' may be passive voice. Use active voice if you can.

[write-good.Passive] 'be used' may be passive voice. Use active voice if you can.

[Google.We] Try to avoid using first-person plural like 'we'.

[Google.Headings] 'A. Creating a repository on GitHub' should use sentence-style capitalization.

[Google.Headings] 'B. Uploading Files to the repository' should use sentence-style capitalization.

[Google.WordList] Use 'click' or 'click in' instead of 'click on'.

[Google.WordList] Use 'URL' instead of 'url'.

[Google.Headings] 'D. Deploy the Site' should use sentence-style capitalization.

[Google.WordList] Use 'click' or 'click in' instead of 'click on'.

[write-good.Passive] 'is done' may be passive voice. Use active voice if you can.

[Google.Will] Avoid using 'will'.

[Google.Headings] 'Assets Used & Produced' should use sentence-style capitalization.

[write-good.Passive] 'is intended' may be passive voice. Use active voice if you can.

[write-good.Passive] 'be used' may be passive voice. Use active voice if you can.

[write-good.TooWordy] 'inception' is too wordy.

[write-good.Weasel] 'various' is a weasel word!

[write-good.Passive] 'are used' may be passive voice. Use active voice if you can.

[write-good.Passive] 'are described' may be passive voice. Use active voice if you can.

[Google.Headings] 'Assets Used' should use sentence-style capitalization.

[Google.OxfordComma] Use the Oxford comma in 'Research software often deals with datasets used for experimentation, analysis or'.

[write-good.Passive] 'is used' may be passive voice. Use active voice if you can.

[write-good.Passive] 'is used' may be passive voice. Use active voice if you can.

[write-good.TooWordy] 'prioritize' is too wordy.

[Google.OxfordComma] Use the Oxford comma in 'By documenting the inclusion of these libraries, developers and'.

[Google.Headings] 'Assets Produced' should use sentence-style capitalization.

[write-good.TooWordy] 'all of' is too wordy.

[write-good.Passive] 'be executed' may be passive voice. Use active voice if you can.

[write-good.TooWordy] 'facilitate' is too wordy.

[write-good.Weasel] 'various' is a weasel word!

[write-good.TooWordy] 'validate' is too wordy.

[write-good.TooWordy] 'demonstrate' is too wordy.

[Google.OxfordComma] Use the Oxford comma in 'Depending on the nature of the research, the software may produce data, results or other outputs that contribute to the research findings, Also included are publications or reports that describe the research, including the software, algorithms and'.

[Google.Will] Avoid using 'will'.

[write-good.Passive] 'be tailored' may be passive voice. Use active voice if you can.

[Google.Headings] 'Preservation & Sustainability' should use sentence-style capitalization.

[Google.OxfordComma] Use the Oxford comma in 'Preservation and sustainability in research software management refer to practices and strategies aimed at ensuring the long-term availability, usability and'.

[write-good.Passive] 'be stored' may be passive voice. Use active voice if you can.

[write-good.Passive] 'be maintained' may be passive voice. Use active voice if you can.

[write-good.Passive] 'be released' may be passive voice. Use active voice if you can.

[Google.Will] Avoid using 'will'.

[Google.Will] Avoid using 'will'.

[write-good.Passive] 'is improved' may be passive voice. Use active voice if you can.

[write-good.Passive] 'are indexed' may be passive voice. Use active voice if you can.

[write-good.Passive] 'be used' may be passive voice. Use active voice if you can.

[write-good.Weasel] 'clearly' is a weasel word!

[write-good.Passive] 'be included' may be passive voice. Use active voice if you can.

[write-good.Passive] 'be bundled' may be passive voice. Use active voice if you can.

[write-good.Passive] 'are used' may be passive voice. Use active voice if you can.

[write-good.TooWordy] 'In addition' is too wordy.

[write-good.Passive] 'be retrieved' may be passive voice. Use active voice if you can.

[write-good.TooWordy] 'overall' is too wordy.

[Google.Will] Avoid using 'will'.

[write-good.Passive] 'is required' may be passive voice. Use active voice if you can.

[write-good.TooWordy] 'demonstrate' is too wordy.

[write-good.Illusions] 'the' is repeated!

[Google.WordList] Use 'preceding' instead of 'above'.

[Google.OxfordComma] Use the Oxford comma in 'The software documentation should include detailed instructions on how to install, configure, use and'.

[Google.OxfordComma] Use the Oxford comma in 'Replay future users and maintainers understand the software's functionality, dependencies and'.

[Google.WordList] Use 'capability' or 'feature' instead of 'functionality'.

[Google.OxfordComma] Use the Oxford comma in 'Preserved research software should include everything needed to reproduce the environment, execution and'.

[Google.OxfordComma] Use the Oxford comma in 'Continuously improved research software requires ongoing maintenance and updates to address bugs, security vulnerabilities, and changing dependencies, environments and'.

[Google.OxfordComma] Use the Oxford comma in 'In addition, encouraging and'.

[write-good.TooWordy] 'In addition' is too wordy.

[Google.Will] Avoid using 'will'.

[write-good.Passive] 'be documented' may be passive voice. Use active voice if you can.

[Google.Will] Avoid using 'will'.

[write-good.Passive] 'be created' may be passive voice. Use active voice if you can.

[Google.OxfordComma] Use the Oxford comma in 'A user manual, also known as a user guide or instruction manual, is a document that provides instructions, information and'.

[write-good.TooWordy] 'assistance' is too wordy.

[write-good.TooWordy] 'It is' is too wordy.

[Google.OxfordComma] Use the Oxford comma in 'It is designed to assist users in understanding the features, functionality and'.

[write-good.Passive] 'is designed' may be passive voice. Use active voice if you can.

[Google.WordList] Use 'capability' or 'feature' instead of 'functionality'.

[Google.OxfordComma] Use the Oxford comma in 'In contrast, a developer manual or programming guide is a document that provides detailed information, instructions and guidelines specifically targeted to other research software developers who may be involved in the development, customization or'.

[write-good.Passive] 'be involved' may be passive voice. Use active voice if you can.

[write-good.TooWordy] 'implement' is too wordy.

[Google.OxfordComma] Use the Oxford comma in 'Like a software management plan, user and'.

[write-good.Passive] 'be reviewed' may be passive voice. Use active voice if you can.

[Google.Headings] 'Version Control Protocol' should use sentence-style capitalization.

[Google.Will] Avoid using 'will'.

[write-good.Passive] 'be used' may be passive voice. Use active voice if you can.

[Google.OxfordComma] Use the Oxford comma in 'A branching strategy dictates how branches in the project are created, managed and'.

[write-good.Passive] 'are created' may be passive voice. Use active voice if you can.

[write-good.TooWordy] 'Overall' is too wordy.

[Google.We] Try to avoid using first-person plural like 'our'.

[write-good.TooWordy] 'implement' is too wordy.

[write-good.TooWordy] 'obtain' is too wordy.

[Google.Will] Avoid using 'will'.

[write-good.TooWordy] 'exclusively' is too wordy.

[write-good.Passive] 'be stored' may be passive voice. Use active voice if you can.

[write-good.Passive] 'be transmitted' may be passive voice. Use active voice if you can.

[write-good.Passive] 'are hosted' may be passive voice. Use active voice if you can.

[Google.OxfordComma] Use the Oxford comma in 'Third parties may have secondary services, servers or'.

[Google.OxfordComma] Use the Oxford comma in 'All of these data hosting and transmission locations are relevant when evaluating data security, privacy and'.

[write-good.TooWordy] 'All of' is too wordy.

[write-good.Passive] 'be considered' may be passive voice. Use active voice if you can.

[write-good.Passive] 'be developed' may be passive voice. Use active voice if you can.

[write-good.Weasel] 'very' is a weasel word!

[write-good.Passive] 'be documented' may be passive voice. Use active voice if you can.

[Google.Headings] 'Licensing & Legal Compliance' should use sentence-style capitalization.

[write-good.Passive] 'is intended' may be passive voice. Use active voice if you can.

[Google.WordList] Use 'open source' instead of 'open-source'.

[write-good.TooWordy] 'It is' is too wordy.

[Google.WordList] Use 'app' instead of 'application'.

[write-good.TooWordy] 'It is' is too wordy.

[write-good.Passive] 'is encouraged' may be passive voice. Use active voice if you can.

[write-good.Passive] 'are carried' may be passive voice. Use active voice if you can.

[write-good.Passive] 'are carried' may be passive voice. Use active voice if you can.

[Google.FirstPerson] Avoid first-person pronouns such as ' I '.

[Google.FirstPerson] Avoid first-person pronouns such as 'my'.

[write-good.TooWordy] 'it is' is too wordy.

[write-good.Passive] 'is recommended' may be passive voice. Use active voice if you can.

[write-good.TooWordy] 'in the case of' is too wordy.

[write-good.Passive] 'be avoided' may be passive voice. Use active voice if you can.

[Google.We] Try to avoid using first-person plural like 'our'.

[write-good.Passive] 'were designed' may be passive voice. Use active voice if you can.

[Google.WordList] Use 'open source' instead of 'open-source'.

[Google.OxfordComma] Use the Oxford comma in 'These practices help ensure the fair, responsible and'.

[Google.OxfordComma] Use the Oxford comma in 'Proper research software deposit and sharing are increasingly recognized as best practice to support open research, reproducibility, research integrity, collaboration and'.

[write-good.Passive] 'being discussed' may be passive voice. Use active voice if you can.

[Google.Will] Avoid using 'will'.

[Google.We] Try to avoid using first-person plural like 'US'.

[Google.Headings] 'FAIR Research Software Checklist' should use sentence-style capitalization.

[write-good.TooWordy] 'acquire' is too wordy.

[Google.WordList] Use 'app' instead of 'application'.

[write-good.Weasel] 'clearly' is a weasel word!

[Google.Headings] 'Further Readings' should use sentence-style capitalization.

[Google.Headings] 'Land Acknowledgement' should use sentence-style capitalization.

[Google.OxfordComma] Use the Oxford comma in 'Wampum belts are beads bound onto strings which narrate Haudenosaunee history, tradition and'.

[write-good.Passive] 'was created' may be passive voice. Use active voice if you can.

[Google.Headings] 'Software Management Plan (SMP)' should use sentence-style capitalization.

[Google.Will] Avoid using 'will'.

[write-good.Passive] 'is intended' may be passive voice. Use active voice if you can.

[Google.Will] Avoid using 'will'.

[write-good.Passive] 'be delivered' may be passive voice. Use active voice if you can.

[Google.Will] Avoid using 'will'.

[write-good.Passive] 'be supported' may be passive voice. Use active voice if you can.

[write-good.Passive] 'is completed' may be passive voice. Use active voice if you can.

[Google.Will] Avoid using 'will'.

[write-good.Passive] 'be needed' may be passive voice. Use active voice if you can.

[write-good.TooWordy] 'However' is too wordy.

[write-good.Weasel] 'clearly' is a weasel word!

[write-good.TooWordy] 'employ' is too wordy.

[Google.Headings] 'Why you may need a Software Management Plan?' should use sentence-style capitalization.

[write-good.Weasel] 'several' is a weasel word!

[write-good.TooWordy] 'minimize' is too wordy.

[write-good.Passive] 'be addressed' may be passive voice. Use active voice if you can.

[Google.Headings] 'Reproducibility Goal' should use sentence-style capitalization.

[write-good.Passive] 'be applied' may be passive voice. Use active voice if you can.

[write-good.Passive] 'be used' may be passive voice. Use active voice if you can.

[write-good.Passive] 'is intended' may be passive voice. Use active voice if you can.

[write-good.Passive] 'is intended' may be passive voice. Use active voice if you can.

[write-good.Passive] 'be applied' may be passive voice. Use active voice if you can.

[write-good.Passive] 'is used' may be passive voice. Use active voice if you can.

[Google.OxfordComma] Use the Oxford comma in 'Reproducible research software is a key component of making research more transparent, reliable and'.

[Google.OxfordComma] Use the Oxford comma in 'It emphasizes the importance of providing comprehensive and detailed documentation, code and'.

[write-good.TooWordy] 'validate' is too wordy.

[Google.OxfordComma] Use the Oxford comma in 'In the context of software development, reproducible research software refers to the creation of software systems and tools that facilitate the reproducibility of scientific experiments, analyses and'.

[write-good.TooWordy] 'facilitate' is too wordy.

[write-good.TooWordy] 'validate' is too wordy.

[Google.Headings] 'Learning Outcome' should use sentence-style capitalization.

[Google.Will] Avoid using 'will'.

[write-good.TooWordy] 'comply with' is too wordy.

[Google.WordList] Use 'open source' instead of 'open-source'.

[Google.Headings] 'Research Software Development Learning Module' should use sentence-style capitalization.

[Google.Colons] ': R' should be in lowercase.

[write-good.Passive] 'is made' may be passive voice. Use active voice if you can.

[Google.Headings] 'Support Guide' should use sentence-style capitalization.

[write-good.Passive] 'is created' may be passive voice. Use active voice if you can.

[Google.Headings] 'FAIR Software' should use sentence-style capitalization.

[Google.OxfordComma] Use the Oxford comma in 'FAIR software is research software which meets the principles of findability, accessibility, interoperability and'.

The github-pages gem can't satisfy your Gemfile's dependencies. If you want to use a different Jekyll version or need additional dependencies, consider building Jekyll site with GitHub Actions: https://jekyllrb.com/docs/continuous-integration/github-actions/

[write-good.Passive] 'were developed' may be passive voice. Use active voice if you can.

[write-good.TooWordy] 'facilitate' is too wordy.

[write-good.Passive] 'be used' may be passive voice. Use active voice if you can.

[Google.OxfordComma] Use the Oxford comma in 'Interoperability refers to the ability of research software to work seamlessly with other tools, systems and'.

[write-good.Passive] 'is designed' may be passive voice. Use active voice if you can.

[Google.OxfordComma] Use the Oxford comma in 'It should be modular, well-structured and accompanied by appropriate documentation, examples and test cases to make it easier for others to understand, modify and'.

[write-good.TooWordy] 'modify' is too wordy.

[Google.OxfordComma] Use the Oxford comma in 'By following the FAIR principles, research software becomes more transparent, collaborative and'.

[Google.OxfordComma] Use the Oxford comma in 'It also fosters a culture of openness, sharing and'.

[Google.Headings] 'Selecting Libraries for Reproducible Software Projects' should use sentence-style capitalization.

[Google.WordList] Use 'capability' or 'feature' instead of 'functionality'.

[Google.We] Try to avoid using first-person plural like 'we'.

[Google.Headings] 'Key Considerations for Selection' should use sentence-style capitalization.

[write-good.TooWordy] 'Minimize' is too wordy.

[Google.OxfordComma] Use the Oxford comma in 'Limiting the size of the technology stack reduces the risk of dependencies becoming outdated, unsupported or'.

[write-good.Passive] 'be stored' may be passive voice. Use active voice if you can.

[write-good.Passive] 'are stored' may be passive voice. Use active voice if you can.

[write-good.Passive] 'are retrieved' may be passive voice. Use active voice if you can.

[Google.Will] Avoid using 'will'.

[Google.OxfordComma] Use the Oxford comma in 'Packages require clear instructions for installation, configuration and'.

[Google.OxfordComma] Use the Oxford comma in 'This knowledge may not be available in the future and a community of support may have ended, which makes it difficult to revive, modify or'.

[write-good.TooWordy] 'modify' is too wordy.

[write-good.Passive] 'be localized' may be passive voice. Use active voice if you can.

[Google.OxfordComma] Use the Oxford comma in 'A broad, active community can helps by providing support, updates and'.

[write-good.TooWordy] 'modify' is too wordy.

[write-good.Passive] 'be redistributed' may be passive voice. Use active voice if you can.

[Google.Will] Avoid using 'will'.

[write-good.TooWordy] 'it is' is too wordy.

[Google.WordList] Use 'Google Cloud Platform' or 'GCP' instead of 'Cloud'.

[write-good.Passive] 'be preserved' may be passive voice. Use active voice if you can.

[Google.Will] Avoid using 'will'.

[write-good.Passive] 'be executed' may be passive voice. Use active voice if you can.

[write-good.TooWordy] 'evaluate' is too wordy.

[Google.Headings] 'Reproducible Computer Code' should use sentence-style capitalization.

[Google.We] Try to avoid using first-person plural like 'we'.

[Google.Will] Avoid using 'will'.

[Google.Headings] 'General & Technical Practices' should use sentence-style capitalization.

[Google.Headings] 'Documentation in Source Code' should use sentence-style capitalization.

[write-good.TooWordy] 'It is' is too wordy.

[write-good.TooWordy] 'it is' is too wordy.

[write-good.Passive] 'are called' may be passive voice. Use active voice if you can.

[Google.Will] Avoid using 'will'.

[write-good.Passive] 'is set' may be passive voice. Use active voice if you can.

[write-good.Passive] 'is set' may be passive voice. Use active voice if you can.

[write-good.Passive] 'be interested' may be passive voice. Use active voice if you can.

[write-good.Passive] 'are integrated' may be passive voice. Use active voice if you can.

[Google.Headings] 'Version Control Audit' should use sentence-style capitalization.

[write-good.Passive] 'be interested' may be passive voice. Use active voice if you can.

[write-good.Passive] 'is designed' may be passive voice. Use active voice if you can.

[write-good.Passive] 'be facilitated' may be passive voice. Use active voice if you can.

[write-good.Passive] 'were made' may be passive voice. Use active voice if you can.

[Google.Headings] 'Interoperable Software Design' should use sentence-style capitalization.

[write-good.Passive] 'is designed' may be passive voice. Use active voice if you can.

[write-good.Passive] 'be reused' may be passive voice. Use active voice if you can.

[write-good.TooWordy] 'utilize' is too wordy.

[Google.WordList] Use 'open source' instead of 'open-source'.

[Google.Headings] 'Use of Non-proprietary and Lossless Formats' should use sentence-style capitalization.

[write-good.TooWordy] 'In addition' is too wordy.

[write-good.Passive] 'is encouraged' may be passive voice. Use active voice if you can.

[write-good.Passive] 'are stored' may be passive voice. Use active voice if you can.

[Google.Will] Avoid using 'will'.

[write-good.Passive] 'be lost' may be passive voice. Use active voice if you can.

[write-good.Passive] 'are needed' may be passive voice. Use active voice if you can.

[write-good.TooWordy] 'in addition' is too wordy.

[Google.Headings] 'Dependency Preservation' should use sentence-style capitalization.

[write-good.TooWordy] 'objective' is too wordy.

[Google.Headings] 'More Formats to Preserve' should use sentence-style capitalization.

[Google.OxfordComma] Use the Oxford comma in 'A source code repository management service provides a centralized location for storing, managing and'.

[write-good.TooWordy] 'facilitate' is too wordy.

[write-good.Passive] 'be built' may be passive voice. Use active voice if you can.

[Google.WordList] Use 'app' instead of 'application'.

[write-good.Passive] 'are used' may be passive voice. Use active voice if you can.

[write-good.Passive] 'are centralised' may be passive voice. Use active voice if you can.

[Google.WordList] Use 'open source' instead of 'open-source'.

[Google.OxfordComma] Use the Oxford comma in 'It serves as a platform for developers and users to discover, download, install, and manage software libraries, frameworks, tools or'.

[Google.WordList] Use 'preceding' instead of 'above'.

[Google.OxfordComma] Use the Oxford comma in 'The Netherlands eScience Center developed the open-source research software directory to promote visibility, findability, impact and'.

[Google.WordList] Use 'open source' instead of 'open-source'.

[Google.Headings] 'Software Testing' should use sentence-style capitalization.

[Google.OxfordComma] Use the Oxford comma in 'Research software often relies on external libraries, frameworks or'.

[write-good.Passive] 'be obtained' may be passive voice. Use active voice if you can.

[write-good.TooWordy] 'validate' is too wordy.

[Google.OxfordComma] Use the Oxford comma in 'This collaborative approach fosters transparency, trust and'.

[write-good.Passive] 'be carried' may be passive voice. Use active voice if you can.

[Google.OxfordComma] Use the Oxford comma in 'Consider implementing a formal test plan, including unit, regression and'.

[write-good.Weasel] 'Clearly' is a weasel word!

[write-good.TooWordy] 'regarding' is too wordy.

[Google.We] Try to avoid using first-person plural like 'our'.

[write-good.Passive] 'be bound' may be passive voice. Use active voice if you can.

[write-good.Passive] 'be interpreted' may be passive voice. Use active voice if you can.

[Google.Acronyms] Spell out 'ORCID', if it's unfamiliar to the audience.

[Google.Acronyms] Spell out 'ORCID', if it's unfamiliar to the audience.

[Google.Contractions] Use 'it's' instead of 'It is'.

[write-good.E-Prime] Try to avoid using 'is'.

[Google.Acronyms] Spell out 'DOI', if it's unfamiliar to the audience.

[Google.Acronyms] Spell out 'DOI', if it's unfamiliar to the audience.

[Google.Acronyms] Spell out 'ORCID', if it's unfamiliar to the audience.

[Google.Passive] In general, use active voice instead of passive voice ('is assigned').

[write-good.E-Prime] Try to avoid using 'is'.

[Google.Acronyms] Spell out 'ORCID', if it's unfamiliar to the audience.

[Google.Acronyms] Spell out 'ORCID', if it's unfamiliar to the audience.

[Google.Acronyms] Spell out 'ORCID', if it's unfamiliar to the audience.

[Google.Acronyms] Spell out 'ORCID', if it's unfamiliar to the audience.

[Google.Contractions] Use 'it's' instead of 'It is'.

[write-good.E-Prime] Try to avoid using 'is'.

[write-good.E-Prime] Try to avoid using 'is'.

[write-good.E-Prime] Try to avoid using 'is'.

[write-good.E-Prime] Try to avoid using 'is'.

[write-good.E-Prime] Try to avoid using 'is'.

[write-good.E-Prime] Try to avoid using 'being'.

[write-good.E-Prime] Try to avoid using 'is'.

[write-good.E-Prime] Try to avoid using 'is'.

[Google.Acronyms] Spell out 'UBC', if it's unfamiliar to the audience.

[write-good.E-Prime] Try to avoid using 'is'.

[write-good.E-Prime] Try to avoid using 'be'.

[Google.Passive] In general, use active voice instead of passive voice ('be added').

[write-good.E-Prime] Try to avoid using 'is'.

[write-good.E-Prime] Try to avoid using 'is'.

[write-good.E-Prime] Try to avoid using 'are'.

[write-good.E-Prime] Try to avoid using 'are'.

[write-good.E-Prime] Try to avoid using 'Be'.

[Google.Acronyms] Spell out 'LTS', if it's unfamiliar to the audience.

[Google.Parens] Use parentheses judiciously.

[write-good.E-Prime] Try to avoid using 'are'.

[write-good.E-Prime] Try to avoid using 'was'.

[write-good.E-Prime] Try to avoid using 'be'.

[Google.Passive] In general, use active voice instead of passive voice ('be asked').

[write-good.E-Prime] Try to avoid using 'been'.

[Google.Passive] In general, use active voice instead of passive voice ('been created').

[write-good.E-Prime] Try to avoid using 'be'.

[Google.Passive] In general, use active voice instead of passive voice ('be used').

[Google.Parens] Use parentheses judiciously.

[Google.Acronyms] Spell out 'ORCID', if it's unfamiliar to the audience.

[Google.Acronyms] Spell out 'ORCID', if it's unfamiliar to the audience.