Update how-to-submit-and-publish-an-article.md (#9555)

Added Jarod as the DRI for review.

# Checklist for submitter

If some of the following don't apply, delete the relevant line.

- [ ] Changes file added for user-visible changes in `changes/` or
`orbit/changes/`.
See [Changes
files](https://fleetdm.com/docs/contributing/committing-changes#changes-files)
for more information.
- [ ] Documented any API changes (docs/Using-Fleet/REST-API.md or
docs/Contributing/API-for-contributors.md)
- [ ] Documented any permissions changes
- [ ] Input data is properly validated, `SELECT *` is avoided, SQL
injection is prevented (using placeholders for values in statements)
- [ ] Added support on fleet's osquery simulator `cmd/osquery-perf` for
new osquery data ingestion features.
- [ ] Added/updated tests
- [ ] Manual QA for all new/changed functionality
  - For Orbit and Fleet Desktop changes:
- [ ] Manual QA must be performed in the three main OSs, macOS, Windows
and Linux.
- [ ] Auto-update manual QA, from released version of component to new
version (see [tools/tuf/test](../tools/tuf/test/README.md)).

handbook/marketing/how-to-submit-and-publish-an-article.md

@@ -8,14 +8,14 @@ This guide includes everything you need to know about Fleet’s editorial proces
 
 | Activity | DRI |
 |:---------|:----|
-| Assign & schedule | Chris McGillicuddy |
-| Review | Chris McGillicuddy |
+| Assign | Jarod Reyes |
+| Review | Jarod Reyes |
 | Artwork | Mike Thomas |
-| Publication | Jarod Reyes |
+| Schedule & Publish | Drew Baker |
 
 ## Who can publish articles?
 
-Everyone is welcome to suggest article ideas or submit drafts. Reach out to Chris McGillicuddy in [#help-content-calendar](https://fleetdm.slack.com/archives/C03PH3BBVSM) on Slack, and include a summary of your idea in the thread.
+Everyone is welcome to suggest article ideas or submit drafts. Reach out to Jarod Reyes in [#help-content-calendar](https://fleetdm.slack.com/archives/C03PH3BBVSM) on Slack, and include a summary of your idea in the thread.
 
 ## Communication
 
@@ -23,11 +23,11 @@ Use the [#help-content-calendar](https://fleetdm.slack.com/archives/C03PH3BBVSM)
 
 ## Schedule
 
-Publishing occurs according to our [content calendar](https://docs.google.com/spreadsheets/d/1IzpoIfTc7cqc9g8w20fQfap3GFcrqgOaiPrpCkowcvA/edit?usp=sharing). However, publication dates are subject to change based on the news or information that needs to be posted. For time-sensitive articles, consult with Chris McGillicuddy in [#help-content-calendar](https://fleetdm.slack.com/archives/C03PH3BBVSM) on Slack.
+Publishing occurs according to our [content calendar](https://docs.google.com/spreadsheets/d/1IzpoIfTc7cqc9g8w20fQfap3GFcrqgOaiPrpCkowcvA/edit?usp=sharing). However, publication dates are subject to change based on the news or information that needs to be posted. For time-sensitive articles, consult with Jarod Reyes in [#help-content-calendar](https://fleetdm.slack.com/archives/C03PH3BBVSM) on Slack.
 
 ## How to submit an article
 
-1. Submit your draft to Chris McGillicuddy as a Google Doc. 
+1. Submit your draft to Jarod Reyes as a Google Doc. 
 2. Include any relevant images, image suggestions, or other design requests you may have.
 
 ## Review process
@@ -50,13 +50,13 @@ Articles are official Fleet communication. We carefully review published content
 
 ## Create a PR for your article
 
-After your article has been editied and approved, create a pull request on fleetdm.com and request review from Chris McGillicuddy.
+After your article has been editied and approved, create a pull request on fleetdm.com and request review from Jarod Reyes.
 
 ### How to PR your article   
 
 1. Familiarize yourself with our [article formatting guide](./article-formatting-guide).
 2. Add a file, formatted in [Markdown](./markdown-guide), to the Fleet repo in Github [fleetdm/fleet/articles](https://github.com/fleetdm/fleet/tree/main/articles), using the name of your article as the filename. E.g., `deploy-fleet-on-render.md`.
-3. Request a review from Chris McGillicuddy. 
+3. Request a review from Jarod Reyes. 
 
 > **IMPORTANT**: Your PR is not confidential. If the information in your article is confidential, please prepare your article in a Google Doc, or create a draft PR ~1 hour before publication time to keep your article private.
 
@@ -81,5 +81,5 @@ After your article is published, the Growth team will schedule your post to be p
 - [Markdown guide](./markdown-guide)
 - [Content style guide](./content-style-guide)
 
-<meta name="maintainedBy" value="chris-mcgillicuddy">
+<meta name="maintainedBy" value="jarodreyes">
 <meta name="title" value="How to submit and publish an article">