General updates and validation of config blocks documentation (#3722) (#3760)

* Updage and align config blocks doc style

* Fix broken links

* Update sorting of log levels

* Update docs/sources/reference/config-blocks/remotecfg.md



---------


(cherry picked from commit 84c4a53)

Co-authored-by: Sam DeHaan <[email protected]>

Author: clayton-cornell

docs/sources/reference/config-blocks/argument.md

@@ -1,21 +1,24 @@
 ---
 canonical: https://grafana.com/docs/alloy/latest/reference/config-blocks/argument/
 description: Learn about the argument configuration block
-menuTitle: argument
-title: argument block
+labels:
+  stage: general-availability
+  products:
+    - oss
+title: argument
 ---
 
-# argument block
+# `argument`
 
 `argument` is an optional configuration block used to specify parameterized input to a [custom component][].
 `argument` blocks must be given a label which determines the name of the argument.
 
 The `argument` block may only be specified inside the definition of [a `declare` block][declare].
 
-## Example
+## Usage
 
 ```alloy
-argument "ARGUMENT_NAME" {}
+argument "<ARGUMENT_NAME>" {}
 ```
 
 ## Arguments
@@ -25,13 +28,13 @@ For clarity, "argument" in this section refers to arguments which can be given t
 "Module argument" refers to the argument being defined for a module, determined by the label of the argument block.
 {{< /admonition >}}
 
-The following arguments are supported:
+You can use the following arguments with `argument`:
 
-Name       | Type     | Description                          | Default | Required
------------|----------|--------------------------------------|---------|---------
-`comment`  | `string` | Description for the argument.        | `false` | no
-`default`  | `any`    | Default value for the argument.      | `null`  | no
-`optional` | `bool`   | Whether the argument may be omitted. | `false` | no
+| Name       | Type     | Description                          | Default | Required |
+| ---------- | -------- | ------------------------------------ | ------- | -------- |
+| `comment`  | `string` | Description for the argument.        | `""`    | no       |
+| `default`  | `any`    | Default value for the argument.      | `null`  | no       |
+| `optional` | `bool`   | Whether the argument may be omitted. | `false` | no       |
 
 By default, all module arguments are required.
 The `optional` argument can be used to mark the module argument as optional.
@@ -41,9 +44,9 @@ When `optional` is `true`, the initial value for the module argument is specifie
 
 The following fields are exported and can be referenced by other components:
 
-Name    | Type  | Description
---------|-------|-----------------------------------
-`value` | `any` | The current value of the argument.
+| Name    | Type  | Description                        |
+| ------- | ----- | ---------------------------------- |
+| `value` | `any` | The current value of the argument. |
 
 If you use a custom component, you are responsible for determining the values for arguments.
 Other expressions within a custom component may use `argument.ARGUMENT_NAME.value` to retrieve the value you provide.

docs/sources/reference/config-blocks/declare.md

@@ -1,20 +1,23 @@
 ---
 canonical: https://grafana.com/docs/alloy/latest/reference/config-blocks/declare/
 description: Learn about the declare configuration block
-menuTitle: declare
-title: declare block
+labels:
+  stage: general-availability
+  products:
+    - oss
+title: declare
 ---
 
-# declare block
+# `declare`
 
 `declare` is an optional configuration block used to define a new [custom component][].
 `declare` blocks must be given a label that determines the name of the custom component.
 
-## Example
+## Usage
 
 ```alloy
-declare "COMPONENT_NAME" {
-    COMPONENT_DEFINITION
+declare "<COMPONENT_NAME>" {
+    <COMPONENT_DEFINITION>
 }
 ```
 
@@ -24,10 +27,10 @@ The `declare` block has no predefined schema for its arguments.
 The body of the `declare` block is used as the component definition.
 The body can contain the following:
 
-* [argument][] blocks
-* [export][] blocks
-* [declare][] blocks
-* [import][] blocks
+* [`argument`][argument] blocks
+* [`export`][export] blocks
+* [`declare`][declare] blocks
+* [`import`][import] blocks
 * Component definitions (either built-in or custom components)
 
 The `declare` block may not contain any configuration blocks that aren't listed above.
@@ -63,7 +66,7 @@ self_collect "example" {
 
 prometheus.remote_write "example" {
   endpoint {
-    url = REMOTE_WRITE_URL
+    url = <REMOTE_WRITE_URL>
   }
 }
 ```

docs/sources/reference/config-blocks/export.md

@@ -1,32 +1,35 @@
 ---
 canonical: https://grafana.com/docs/alloy/latest/reference/config-blocks/export/
 description: Learn about the export configuration block
-menuTitle: export
-title: export block
+labels:
+  stage: general-availability
+  products:
+    - oss
+title: export
 ---
 
-# export block
+# `export`
 
 `export` is an optional configuration block used to specify an emitted value of a [custom component][].
 `export` blocks must be given a label which determine the name of the export.
 
 The `export` block may only be specified inside the definition of [a `declare` block][declare].
 
-## Example
+## Usage
 
 ```alloy
-export "ARGUMENT_NAME" {
-  value = ARGUMENT_VALUE
+export "<ARGUMENT_NAME>" {
+  value = <ARGUMENT_VALUE>
 }
 ```
 
 ## Arguments
 
-The following arguments are supported:
+You can use the following arguments with `export`:
 
-Name    | Type  | Description      | Default | Required
---------|-------|------------------|---------|---------
-`value` | `any` | Value to export. |         | yes
+| Name    | Type  | Description      | Default | Required |
+| ------- | ----- | ---------------- | ------- | -------- |
+| `value` | `any` | Value to export. |         | yes      |
 
 The `value` argument determines what the value of the export is.
 To expose an exported field of another component, set `value` to an expression that references that exported value.
@@ -46,7 +49,7 @@ declare "pods_and_nodes" {
   }
 
   discovery.kubernetes "nodes" {
-    role = "nodes"
+    role = "node"
   }
 
   export "kubernetes_resources" {

docs/sources/reference/config-blocks/foreach.md

@@ -1,13 +1,15 @@
 ---
-canonical: https://grafana.com/docs/alloy/latest/reference/stdlib/foreach/
-description: Learn about foreach
+canonical: https://grafana.com/docs/alloy/latest/reference/config-blocks/foreach/
+description: Learn about the foreach configuration block
 labels:
   stage: experimental
+  products:
+    - oss
 menuTitle: foreach
 title: foreach
 ---
 
-# foreach
+# `foreach`
 
 {{< docs/shared lookup="stability/experimental_feature.md" source="alloy" version="<ALLOY_VERSION>" >}}
 
@@ -68,29 +70,28 @@ This results in component paths like the following:
 /foreach.pods/foreach_app-2_1/component.default
 ```
 
-If the collection item is not a object or the specified field doesn't exist, it falls back to using the entire item for identification.
+If the collection item isn't an object or the specified field doesn't exist, it falls back to using the entire item for identification.
 {{< /admonition >}}
 
-[types]: ../../../get-started/configuration-syntax/expressions/types_and_values
+[types]: ../../../get-started/configuration-syntax/expressions/types_and_values/
 
 ## Blocks
 
-You can use the following blocks with `foreach`:
+You can use the following block with `foreach`:
 
-| Block        | Description                  | Required |
-| ------------ | ---------------------------- | -------- |
-| [template][] | A component pipeline to run. | yes      |
+| Block                  | Description                  | Required |
+| ---------------------- | ---------------------------- | -------- |
+| [`template`][template] | A component pipeline to run. | yes      |
 
 [template]: #template
 
 ### `template`
 
-The `template` block contains the definition of {{< param "PRODUCT_NAME" >}} components which will be ran for every item in the collection.
-The contents of the block look like a normal {{< param "PRODUCT_NAME" >}} configuration file,
-except that you can use the keyword defined in `var` to refer to the current item in the collection.
+The `template` block contains the definition of {{< param "PRODUCT_NAME" >}} components used for every item in the collection.
+The contents of the block look like a normal {{< param "PRODUCT_NAME" >}} configuration file, except that you can use the keyword defined in `var` to refer to the current item in the collection.
 
 Components inside the `template` block can use exports of components defined outside of the `foreach` block.
-However, components outside of the `foreach` cannot use exports from components defined inside the `template` block of a `foreach`.
+However, components outside of the `foreach` can't use exports from components defined inside the `template` block of a `foreach`.
 
 ## Example