From 335d8e64239ec75f2cebfc23585d31e1be166b84 Mon Sep 17 00:00:00 2001 From: Mike Thomas <78363703+mike-j-thomas@users.noreply.github.com> Date: Mon, 12 Jun 2023 21:37:14 +0900 Subject: [PATCH] Mike j thomas handbook patch (#12282) Fixed up a couple of typos from my previous PR. --- handbook/marketing/docs-handbook.md | 2 +- handbook/marketing/website-handbook.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/handbook/marketing/docs-handbook.md b/handbook/marketing/docs-handbook.md index b360f9efae..be2e64310a 100644 --- a/handbook/marketing/docs-handbook.md +++ b/handbook/marketing/docs-handbook.md @@ -32,7 +32,7 @@ When creating a pull request for Markdown changes in the docs, request a review ## Markdown -The Fleet docs are written in Markdown.[Markdown](https://about.gitlab.com/handbook/markdown-guide/). Using Markdown lets us keep our documentation consistently formatted and viewable directly from the Fleet GitHub repo. +The Fleet docs are written in Markdown. Using Markdown lets us keep our documentation consistently formatted and viewable directly from the Fleet GitHub repo. See the [Markdown guide](./markdown-guide) for help formatting Fleet-flavored Markdown. diff --git a/handbook/marketing/website-handbook.md b/handbook/marketing/website-handbook.md index 965ca740b6..87525a7ed0 100644 --- a/handbook/marketing/website-handbook.md +++ b/handbook/marketing/website-handbook.md @@ -115,7 +115,7 @@ Once you have the above follow these steps: > **Note:** Some features, such as Fleet Sandbox, Self-service license dispenser, and account creation are not availible when running the website locally. If you need help testing features on a local copy, reach out to `@eashaw` in the [#g-website](https://fleetdm.slack.com/archives/C058S8PFSK0) channel on Slack.. ## Merging changes -When merging a PR to master the master branch of the [Fleet repo](https://github.com/fleetdm/fleet), remember that whatever you merge gets deployed live immediately. Ensure that the appropriate quality checks have been completed before merging. [Learn about the website QA process](#quality). +When merging a PR to the master branch of the [Fleet repo](https://github.com/fleetdm/fleet), remember that whatever you merge gets deployed live immediately. Ensure that the appropriate quality checks have been completed before merging. [Learn about the website QA process](#quality). When merging changes to the [docs](https://fleetdm.com/docs), [handbook](https://fleetdm.com/handbook), and articles, make sure that the PR’s changes do not contain inappropriate content (goes without saying) or confidential information, and that the content represents our [brand](#brand) accordingly. When in doubt reach out to the product manager of the [website group](https://fleetdm.com/handbook/company/product-groups#website-group) in the [#g-website](https://fleetdm.slack.com/archives/C058S8PFSK0) channel on Slack.