From 021aca256c8ff9973b29448240a64ee38f0efe5b Mon Sep 17 00:00:00 2001 From: "lean.dev" <34773040+leandro-deveikis@users.noreply.github.com> Date: Thu, 25 Jan 2024 12:20:20 -0300 Subject: [PATCH] Fix typos (#81270) --- contribute/deprecation-policy.md | 6 +++--- packages/README.md | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/contribute/deprecation-policy.md b/contribute/deprecation-policy.md index a49016588a1..3c305833ab1 100644 --- a/contribute/deprecation-policy.md +++ b/contribute/deprecation-policy.md @@ -26,6 +26,6 @@ Grafana employees can find more details in our internal docs. ## Announced deprecations. -| Name | Annoucement Date | Disabling date | Removal Date | Description | Status | -| ------------------------------------------------------------------------ | ---------------- | -------------- | ------------ | ----------------------------------------------------------------------------------------------------------------------- | ------- | -| [Support for Mysql 5.7](https://github.com/grafana/grafana/issues/68446) | 2023-05-15 | October 2023 | | MySQL 5.7 is being deprecated in October 2023 and Grafana's policy is to test against the officially supported version. | Planned | +| Name | Announcement Date | Disabling date | Removal Date | Description | Status | +| ------------------------------------------------------------------------ | ----------------- | -------------- | ------------ | ----------------------------------------------------------------------------------------------------------------------- | ------- | +| [Support for Mysql 5.7](https://github.com/grafana/grafana/issues/68446) | 2023-05-15 | October 2023 | | MySQL 5.7 is being deprecated in October 2023 and Grafana's policy is to test against the officially supported version. | Planned | diff --git a/packages/README.md b/packages/README.md index d77c6e0c5dc..b90745433ec 100644 --- a/packages/README.md +++ b/packages/README.md @@ -36,7 +36,7 @@ Every commit to main that has changes within the `packages` directory is a subje > All of the steps below must be performed on a release branch, according to Grafana Release Guide. -> You must be logged in to NPM as part of Grafana NPM org before attempting to publish to the npm registery. +> You must be logged in to NPM as part of Grafana NPM org before attempting to publish to the npm registry. 1. Run `yarn packages:clean` script from the root directory. This will delete any previous builds of the packages. 2. Run `yarn packages:prepare` script from the root directory. This performs tests on the packages and prompts for the version of the packages. The version should be the same as the one being released.