From 276c59fd6f1673dc364ee1fb1849b2cb439a03c6 Mon Sep 17 00:00:00 2001 From: Joseph Barnes Date: Wed, 4 Oct 2023 09:48:05 -0500 Subject: [PATCH 1/3] Update _index.md --- docs/content/contributing/_index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/content/contributing/_index.md b/docs/content/contributing/_index.md index 8aef5c847..bc9943851 100644 --- a/docs/content/contributing/_index.md +++ b/docs/content/contributing/_index.md @@ -95,7 +95,7 @@ Please note the following settings in the alert definition: ## Auto-Generated Alert Rules -A script was run to auto-generate alert rules based on top usage and settings trends. These rules have been added the their respective *alerts.yaml* files and have two tags associated with them: *auto-generated* and *agc-xxxx*. The *agc-xxxx* tag indicates the number of results found for that alert rule in the query used to analyze the top trends. This number should be used to evaluate the importantance of including that alert in the repo. Once an auto-generated alert has been verified and updated with reference documenation, the *visible* tag should be updated to true. This will make the alert alert visible on the site. Resoruce categories and types that do not have visible alerts are currently hidden from the table of contents. To make those resource categries and types visible, edit their respective *_index.md* files and remove the *geekdocHidden: true* metadata from the top of the file. +A script was run to automatically generate alert rules based on top usage and settings trends. These rules have been added the their respective *alerts.yaml* files and have two tags associated with them: *auto-generated* and *agc-xxxx*. The *agc-xxxx* tag indicates the number of results found for that alert rule in the query used to analyze the top trends. This number should be used to evaluate the importantance of including that alert rule as guidance in the repo. Once an auto-generated alert rule has been verified and updated with reference documenation, the *visible* property should be set to *true*. This will make the alert rule visible on the site. Resoruce categories and types that do not have visible alerts are currently hidden from the table of contents. To make those resource categories and types visible, edit their respective *_index.md* files and remove the *geekdocHidden: true* metadata from the top of the file. ## Context/Background @@ -194,5 +194,5 @@ Once you have committed changes to your fork of the AMBA repo, you create a pull ## Top Tips 1. Sometimes the local version of the website may show some inconsistencies that don't reflect the content you have created. - - If this happens, simply kill the Hugo local web server by pressing CTRL+C and then restart the Hugo web server by running `hugo server -D` from the root of the repo. + - If this happens, simply kill the Hugo local web server by pressing CTRL+C and then restart the Hugo web server by running `hugo server -D` from the root of the repo. From 5d674cd54af0158ec8c3022117317c261aee271f Mon Sep 17 00:00:00 2001 From: Joseph Barnes Date: Thu, 5 Oct 2023 10:34:36 -0500 Subject: [PATCH 2/3] fixed pselling errors in contrib --- docs/content/contributing/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/contributing/_index.md b/docs/content/contributing/_index.md index bc9943851..3e8a69ccf 100644 --- a/docs/content/contributing/_index.md +++ b/docs/content/contributing/_index.md @@ -95,7 +95,7 @@ Please note the following settings in the alert definition: ## Auto-Generated Alert Rules -A script was run to automatically generate alert rules based on top usage and settings trends. These rules have been added the their respective *alerts.yaml* files and have two tags associated with them: *auto-generated* and *agc-xxxx*. The *agc-xxxx* tag indicates the number of results found for that alert rule in the query used to analyze the top trends. This number should be used to evaluate the importantance of including that alert rule as guidance in the repo. Once an auto-generated alert rule has been verified and updated with reference documenation, the *visible* property should be set to *true*. This will make the alert rule visible on the site. Resoruce categories and types that do not have visible alerts are currently hidden from the table of contents. To make those resource categories and types visible, edit their respective *_index.md* files and remove the *geekdocHidden: true* metadata from the top of the file. +A script was run to automatically generate alert rules based on top usage and settings trends. These rules have been added the their respective *alerts.yaml* files and have two tags associated with them: *auto-generated* and *agc-xxxx*. The *agc-xxxx* tag indicates the number of results found for that alert rule in the query used to analyze the top trends. This number should be used to evaluate the importances of including that alert rule as guidance in the repo. Once an auto-generated alert rule has been verified and updated with reference documenation, the *visible* property should be set to *true*. This will make the alert rule visible on the site. Resoruce categories and types that do not have visible alerts are currently hidden from the table of contents. To make those resource categories and types visible, edit their respective *_index.md* files and remove the *geekdocHidden: true* metadata from the top of the file. ## Context/Background From bfd432ef02b420847ac11819d44e651fd2626647 Mon Sep 17 00:00:00 2001 From: Joseph Barnes Date: Thu, 5 Oct 2023 10:39:21 -0500 Subject: [PATCH 3/3] fixed spelling errors in contrib --- docs/content/contributing/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/contributing/_index.md b/docs/content/contributing/_index.md index 3e8a69ccf..e480b0fc0 100644 --- a/docs/content/contributing/_index.md +++ b/docs/content/contributing/_index.md @@ -95,7 +95,7 @@ Please note the following settings in the alert definition: ## Auto-Generated Alert Rules -A script was run to automatically generate alert rules based on top usage and settings trends. These rules have been added the their respective *alerts.yaml* files and have two tags associated with them: *auto-generated* and *agc-xxxx*. The *agc-xxxx* tag indicates the number of results found for that alert rule in the query used to analyze the top trends. This number should be used to evaluate the importances of including that alert rule as guidance in the repo. Once an auto-generated alert rule has been verified and updated with reference documenation, the *visible* property should be set to *true*. This will make the alert rule visible on the site. Resoruce categories and types that do not have visible alerts are currently hidden from the table of contents. To make those resource categories and types visible, edit their respective *_index.md* files and remove the *geekdocHidden: true* metadata from the top of the file. +A script was run to automatically generate alert rules based on top usage and settings trends. These rules have been added the their respective *alerts.yaml* files and have two tags associated with them: *auto-generated* and *agc-xxxx*. The *agc-xxxx* tag indicates the number of results found for that alert rule in the query used to analyze the top trends. This number should be used to evaluate the importance of including that alert rule as guidance in the repo. Once an auto-generated alert rule has been verified and updated with reference documenation, the *visible* property should be set to *true*. This will make the alert rule visible on the site. Resoruce categories and types that do not have visible alerts are currently hidden from the table of contents. To make those resource categories and types visible, edit their respective *_index.md* files and remove the *geekdocHidden: true* metadata from the top of the file. ## Context/Background