docs: fix formatting

Author: posva

docs/cookbook/migration-v2-v3.md

@@ -117,7 +117,7 @@ app.use(VueFire, {
 
 ## Vuexfire
 
-:::tip
+::: tip
 If you are using [Pinia](https://pinia.vuejs.org/), make sure to check the [Pinia guide](./subscriptions-external.md#pinia) instead.
 :::
 

docs/guide/auth.md

@@ -43,7 +43,7 @@ router.beforeEach(async () => {
 })
 ```
 
-:::tip
+::: tip
 If you are using `getCurrentUser()` in a navigation guard, make sure to add it before calling `app.use(router)` as that will trigger the initial navigation.
 :::
 

docs/guide/getting-started.md

@@ -12,7 +12,7 @@ yarn add vuefire firebase
 npm install vuefire firebase
 ```
 
-:::warning
+::: warning
 
 VueFire requires Firebase JS SDK >= 9 but **is compatible with Vue 2 and Vue 3**. It's currently in alpha, make sure to check [the Roadmap](https://github.com/vuejs/vuefire/issues/1241) and report any issue you find.
 
@@ -38,7 +38,7 @@ export const firestore = getFirestore(firebase)
 // ... other firebase exports
 ```
 
-:::tip
+::: tip
 Note that we will refer to `database` and `firestore` as `db` in examples where only one of them is used.
 :::
 

docs/guide/index.md

@@ -129,7 +129,7 @@ createApp({
 
 </FirebaseExample>
 
-:::warning
+::: warning
 
 - In the [**RTDB** example](#original_rtdb), we are omitting the unsubscribe part because it requires to save the return of every listener created to later on call `this.todosRef.off` with _every single_ one of them.
 - In the [**Firestore** example](#original_firestore), the code above is not taking into account [Firestore references](https://firebase.google.com/docs/firestore/data-model#references) which **considerably** increases the complexity of binding and [is handled transparently](./realtime-data.md#references-firestore-only) by Vuefire

docs/guide/nuxt.md

@@ -1,6 +1,6 @@
 # Nuxt.js
 
-:::warning
+::: warning
 The Nuxt module and this docs are a WIP. Things might not work yet.
 :::
 

docs/guide/old_writing-data.md

@@ -6,7 +6,7 @@ As said in the introduction, Vuefire **does not** handle writing data back to Fi
 
 There are two ways to update a document `set` and `update`. The first will replace the whole document (as a PUT in HTTP) while the later will keep the original document and overwrite values (as a PATCH in HTTP).
 
-:::tip
+::: tip
 In the following examples, `this.user` is a user bound to a Firebase document using Vuefire while `this.conferences` is a list of conferences bound to a Firebase collection using Vuefire.
 :::
 

docs/guide/options-api-realtime-data.md

@@ -1,6 +1,6 @@
 # Options API Realtime Data
 
-:::tip
+::: tip
 This pages assumes you have read the [Realtime Data](./realtime-data.md) page and will only cover the syntax differences between the Options API and the Composition API.
 :::
 
@@ -89,7 +89,7 @@ export default {
 
 </FirebaseExample>
 
-:::warning
+::: warning
 You must declare properties with their initial values in `data`. **For the RTDB, using an _Array_ as the initial value will bind the Reference as an array, otherwise it is bound as an object**. For Firestore, collections and queries are bound as arrays while documents are bound as objects.
 :::
 
@@ -151,7 +151,7 @@ export default {
 
 With the approach above, `user` will always be bound to the user defined by the prop `id`
 
-:::tip
+::: tip
 No need to call `$databaseUnbind`/`$firestoreUnbind` as `$databaseBind`/`$firestoreBind` will automatically unbind any existing binding on the provided key. Upon component removal, all bindings are removed as well, so no need to use `$databaseUnbind`/`$firestoreUnbind` in `unmounted` hooks.
 :::
 

docs/guide/realtime-data.md

@@ -1,6 +1,6 @@
 # Realtime Data
 
-:::info
+::: info
 If you are looking for the VueFire Options API guide, make sure to **also check** the [dedicated page](./options-api-realtime-data.md). This page still includes a more information than the Options API page, which focuses more on its syntax.
 :::
 
@@ -67,7 +67,7 @@ const contact = useDocument(contactSource)
 
 This way, if the route changes, the document will be updated to the new one, automatically unsubscribing from the previous one and subscribing to the new one.
 
-:::tip
+::: tip
 If you can't use a `computed()`, use `shallowRef()`s instead of `ref()`s to store the data sources. This is because `shallowRef()` doesn't try to recursively observe the object it's given, which in the case of a Firebase data source, would be wasteful.
 :::
 
@@ -93,7 +93,7 @@ const {
 
 Notice how we rename `data` to whatever makes more sense for the context. It's important to note
 
-:::note
+::: warning
 All of the properties that can be defined on the Ref are defined as [non-enumerable properties](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/defineProperty) which means they won't be copied over when using the spread operator e.g. `const { data, ...rest } = useDocument(contactSource)`. This is to ensure they are completely ignored in other places like devtools.
 :::
 
@@ -299,7 +299,7 @@ Note this is only a type annotation, it does not perform any runtime validation.
 
 The recommended Firebase approach is to use the `withConverter()` for Firestore:
 
-:::info
+::: info
 `.withConverter()` is a Firestore feature that doesn't have an equivalent in Database but you can use VueFire's [`serialize()` option](#TODO:global options when installing plugin) instead.
 :::
 

docs/guide/ssr.md

@@ -1,7 +1,7 @@
 # Server Side Rendering (SSR)
 
 <!-- NOTE: hide until it works -->
-<!-- :::tip
+<!-- ::: tip
 If you are using Nuxt.js, read the [Nuxt guide](./nuxt.md) instead, most of the things are already configured for you.
 ::: -->
 

docs/guide/upgrading-from-v1.md

@@ -108,7 +108,7 @@ Previously you would call `$firestoreBindAsArray` and `$firestoreBindAsObject` d
 }
 ```
 
-:::tip
+::: tip
 Note: you can pass an options object with `{ bindName: '$firestoreBind', unbindName: '$firestoreUnbind' }` to `Vue.use(VueFire)` to keep a shorter name for binding instead of `$rtdbBind` and `$rtdbUnbind`.
 :::