From 88366b9ed2d5bc9b0b300116f72117a47ec394c2 Mon Sep 17 00:00:00 2001
From: Rich Harris <richard.a.harris@gmail.com>
Date: Sat, 23 Mar 2019 20:56:27 -0400
Subject: [PATCH] typo

---
 site/content/blog/2018-12-27-virtual-dom-is-pure-overhead.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/site/content/blog/2018-12-27-virtual-dom-is-pure-overhead.md b/site/content/blog/2018-12-27-virtual-dom-is-pure-overhead.md
index 062745b192..f70bda43d5 100644
--- a/site/content/blog/2018-12-27-virtual-dom-is-pure-overhead.md
+++ b/site/content/blog/2018-12-27-virtual-dom-is-pure-overhead.md
@@ -121,7 +121,7 @@ function MoreRealisticComponent(props) {
 			<p>Selected {selected ? selected.name : 'nothing'}</p>
 
 			<ul>
-				${props.items.map(item =>
+				{props.items.map(item =>
 					<li>
 						<button onClick={() => setSelected(item)}>
 							{item.name}
@@ -147,4 +147,4 @@ Svelte is explicitly designed to prevent you from ending up in that situation.
 
 It's important to understand that virtual DOM *isn't a feature*. It's a means to an end, the end being declarative, state-driven UI development. Virtual DOM is valuable because it allows you to build apps without thinking about state transitions, with performance that is *generally good enough*. That means less buggy code, and more time spent on creative tasks instead of tedious ones.
 
-But it turns out that we can achieve a similar programming model without using virtual DOM — and that's where Svelte comes in.
\ No newline at end of file
+But it turns out that we can achieve a similar programming model without using virtual DOM — and that's where Svelte comes in.