use aside consistently across the files

Author: Solant

src/content/docs/docs/reference/layers.mdx

@@ -107,7 +107,7 @@ The Widgets layer is intended for large self-sufficient blocks of UI. Widgets ar
 
 If a block of UI makes up most of the interesting content on a page, and is never reused, it **should not be a widget**, and instead it should be placed directly inside that page.
 
-<Aside>
+<Aside type="note">
 
 If you're using a nested routing system (like the router of [Remix][ext-remix]), it may be helpful to use the Widgets layer in the same way as a flat routing system would use the Pages layer — to create full router blocks, complete with related data fetching, loading states, and error boundaries.
 

src/content/docs/docs/reference/public-api.mdx

@@ -4,7 +4,7 @@ sidebar:
   order: 3
 ---
 
-import { FileTree } from '@astrojs/starlight/components';
+import { FileTree, Aside } from '@astrojs/starlight/components';
 
 A public API is a _contract_ between a group of modules, like a slice, and the code that uses it. It also acts as a gate, only allowing access to certain objects, and only through that public API.
 
@@ -55,11 +55,11 @@ import type { EntityA } from "entities/A/@x/B";
 
 The notation `A/@x/B` is meant to be read as "A crossed with B".
 
-:::note
+<Aside type="note">
 
 Try to keep cross-imports to a minimum, and **only use this notation on the Entities layer**, where eliminating cross-imports is often unreasonable.
 
-:::
+</Aside>
 
 ## Issues with index files