fix note

Signed-off-by: Pulak Kanti Bhowmick <[email protected]>

website/docs/core-concepts/stacks/define-components.mdx

@@ -217,9 +217,9 @@ There are two types of components:
 
 The `metadata.enabled` parameter controls whether a component is included in deployment. By default, components are enabled. Setting `metadata.enabled` to `false` skips the component entirely—no workspace is created, and no Terraform commands are executed. Disabling a component does not cause deletion. It just signals that it's no longer managed by Atmos.
 
-<Note>
+:::info Note
 This should not be confused with [Cloud Posse's conventions and best practices](/best-practices/terraform/) of having modules and components define a [Terraform input named `enabled`](/best-practices/terraform/#use-feature-flags-list-or-map-inputs-for-optional-functionality). This is a general convention and `vars.enabled` is not a special variable. Atmos does not treat it differently from any other variable.
-</Note>
+:::
 
 **Example**:
 ```yaml