From 9655a81a8aaf04a97ff9918b4b37b9c911f5f5a1 Mon Sep 17 00:00:00 2001
From: 719media <ben@719media.com>
Date: Sun, 23 Feb 2020 06:48:28 -0800
Subject: [PATCH] docs: attr is data-vmid not just vmid (#519)

Actual output is data-vmid
---
 docs/faq/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/faq/README.md b/docs/faq/README.md
index 1d83f2e..57c39bd 100644
--- a/docs/faq/README.md
+++ b/docs/faq/README.md
@@ -70,7 +70,7 @@ This is not what we want, since the meta `description` needs to be unique for ev
 **Output:**
 ```html
 <meta charset="utf-8">
-<meta vmid="description" name="description" content="bar">
+<meta data-vmid="description" name="description" content="bar">
 ```
 
 While solutions like `react-helmet` manage the occurrence order and merge behaviour for you automatically, it involves a lot more code and is therefore prone to failure in some edge-cases, whereas this method is _almost_ bulletproof because of its versatility; _at the expense of one tradeoff:_ these `vmid` properties will be rendered out in the final markup (`vue-meta` uses these client-side to prevent duplicating or overriding markup). If you are serving your content gzipped, then the slight increase in HTTP payload size is negligible.