From b79e1f9807341a8e5e94420ef764be4a9c8d5ee2 Mon Sep 17 00:00:00 2001
From: skirtle <65301168+skirtles-code@users.noreply.github.com>
Date: Tue, 20 Oct 2020 16:41:27 +0100
Subject: [PATCH] fix: reduce heading levels for Template Refs to match other
 pages

---
 src/guide/composition-api-template-refs.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/src/guide/composition-api-template-refs.md b/src/guide/composition-api-template-refs.md
index 2147757c26..f04674edc8 100644
--- a/src/guide/composition-api-template-refs.md
+++ b/src/guide/composition-api-template-refs.md
@@ -1,4 +1,4 @@
-## Template Refs
+# Template Refs
 
 > This section uses [single-file component](single-file-component.html) syntax for code examples
 
@@ -35,7 +35,7 @@ Here we are exposing `root` on the render context and binding it to the div as i
 
 Refs used as templates refs behave just like any other refs: they are reactive and can be passed into (or returned from) composition functions.
 
-### Usage with JSX
+## Usage with JSX
 
 ```js
 export default {
@@ -53,7 +53,7 @@ export default {
 }
 ```
 
-### Usage inside `v-for`
+## Usage inside `v-for`
 
 Composition API template refs do not have special handling when used inside `v-for`. Instead, use function refs to perform custom handling: