docs: add link to ssrRef documentation from useAsync

nuxt-community · Oct 15, 2020 · a072c94 · a072c94 · vercel · Oct 15, 2020
1 parent 4b82ec7
commit a072c94
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 1 deletion.
diff --git a/docs/content/en/ssrPromise.md b/docs/content/en/ssrPromise.md
@@ -41,6 +41,6 @@ Under the hood, `ssrPromise` requires a key to ensure that the ref values match
 
 <alert>
 
-At the moment, an `ssrPromise` is only suitable for one-offs, unless you provide your own unique key. See [the `ssrRef` documentation](./ssrRef.md) for more information.
+At the moment, an `ssrPromise` is only suitable for one-offs, unless you provide your own unique key. See [the `ssrRef` documentation](/ssrRef) for more information.
 
 </alert>
diff --git a/docs/content/en/useAsync.md b/docs/content/en/useAsync.md
@@ -11,6 +11,8 @@ On the server, this helper will inline the result of the async call in your HTML
 
 However, if the call hasn't been carried out on SSR (such as if you have navigated to the page after initial load), it returns a `null` ref that is filled with the result of the async call when it resolves.
 
+<alert>Note that there are some gotchas when using `ssrRef` (which this helper does) - see [the ssrRef docs](/ssrRef) for more information.</alert>
+
 ```ts
 import { defineComponent, useAsync, useContext } from '@nuxtjs/composition-api'
-Original file line number
+Diff line change
@@ Expand Up @@
     However, if the call hasn't been carried out on SSR (such as if you have navigated to the page after initial load), it returns a `null` ref that is filled with the result of the async call when it resolves.
+    <alert>Note that there are some gotchas when using `ssrRef` (which this helper does) - see [the ssrRef docs](/ssrRef) for more information.</alert>
     ```ts
     import { defineComponent, useAsync, useContext } from '@nuxtjs/composition-api'
@@ Expand Down @@