diff --git a/packages/docs/src/guide-composable/query.md b/packages/docs/src/guide-composable/query.md
index e434972..66720af 100644
--- a/packages/docs/src/guide-composable/query.md
+++ b/packages/docs/src/guide-composable/query.md
@@ -704,22 +704,6 @@ function enableQuery () {
}
```
-### Polling
-
-Polling means repeatedly calling the server to automatically update the query data.
-
-You can enable polling with the `pollInterval` which will be the interval in ms between each requests repeatdly made to the server.
-
-In this example, we will poll the server every second:
-
-```js
-const { result } = useQuery(gql`
- ...
-`, null, {
- pollInterval: 1000,
-})
-```
-
### Fetch Policy
The `fetchPolicy` option allow you to customize how the query will use the Apollo Client cache.
@@ -740,3 +724,77 @@ Available values are:
- `network-only`: return result from network, fail if network call doesn't succeed, save to cache.
- `no-cache`: return result from network, fail if network call doesn't succeed, don't save to cache.
+## Updating cached results
+
+When a query is completed, it will update the cache with the result data (depending on the [fetch policy](#fetch-policy)). This optimize the next time the data needs to be rendered in your application and ensures that all components relying on a piece of data is always consistent.
+
+However, you sometimes want to make sure that this data is up-to-date compared to the server.
+
+### Polling
+
+Polling means repeatedly calling the server to automatically update the query data.
+
+You can enable polling with the `pollInterval` which will be the interval in ms between each requests repeatdly made to the server.
+
+In this example, we will poll the server every second:
+
+```js
+const { result } = useQuery(gql`
+ ...
+`, null, {
+ pollInterval: 1000,
+})
+```
+
+### Refetching
+
+The other way is manually executing the query again in response to an event, as opposed to using a fixed interval.
+
+This is done using the `refetch` function:
+
+```vue{7,24,40}
+
+
+
+