From 9008e2bef8dcd1f2253ae9c5cccf864535135a66 Mon Sep 17 00:00:00 2001 From: Jesse Mostipak Date: Tue, 13 Aug 2024 10:29:35 -0500 Subject: [PATCH] typo --- organization/external-communications.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/organization/external-communications.md b/organization/external-communications.md index d9485dd..24e6b1b 100644 --- a/organization/external-communications.md +++ b/organization/external-communications.md @@ -55,7 +55,7 @@ The following processes for writing a blog post should be used by both pyOpenSci 3. Submit a pull request from your fork of the website repo to [https://github.com/pyOpenSci/pyopensci.github.io](https://github.com/pyOpenSci/pyopensci.github.io). 4. Make sure that the blog post passes CI checks that look for spelling errors, broken links and more. Please note that occasionally the `htmlproofer` check will fail because the URL does not exist yet. We have implemented a fix for this, but it occasionally does not work. 5. Request review of the blog post. A member of the pyOpenSci staff should always review any new content being added to the website. -6. Once you have an approving review, the pull request can be merged. In the case of guest blog posts, a memember of the pyOpenSci team will merge your post. +6. Once you have an approving review, the pull request can be merged. In the case of guest blog posts, a member of the pyOpenSci team will merge your post. pyOpenSci has GitHub organization-wide policies in place that ensure all pull requests are generally reviewed prior to being merged. In some instances we may bypass those if the PR is a small fix or critical update. In most cases a review is preferred. Please contact the Executive Director and Founder, Leah Wasser, with any questions or needs for clarification.