diff --git a/apps/svelte.dev/content/blog/2016-11-26-frameworks-without-the-framework.md b/apps/svelte.dev/content/blog/2016-11-26-frameworks-without-the-framework.md index de7a227082..677273c48a 100644 --- a/apps/svelte.dev/content/blog/2016-11-26-frameworks-without-the-framework.md +++ b/apps/svelte.dev/content/blog/2016-11-26-frameworks-without-the-framework.md @@ -32,7 +32,7 @@ The [Svelte implementation of TodoMVC](https://svelte-todomvc.surge.sh/) weighs And once your app _is_ up and running, according to [js-framework-benchmark](https://github.com/krausest/js-framework-benchmark) **Svelte is fast as heck**. It's faster than React. It's faster than Vue. It's faster than Angular, or Ember, or Ractive, or Preact, or Riot, or Mithril. It's competitive with Inferno, which is probably the fastest UI framework in the world, for now, because [Dominic Gannaway](https://twitter.com/trueadm) is a wizard. (Svelte is slower at removing elements. We're [working on it](https://github.com/sveltejs/svelte/issues/26).) -It's basically as fast as vanilla JS, which makes sense because it _is_ vanilla JS – just vanilla JS that you didn't have to write. +It's basically as fast as vanilla JS, which makes sense because it _is_ vanilla JS – just vanilla JS that you didn't have to write. ## But that's not the important thing diff --git a/apps/svelte.dev/content/blog/2017-09-06-the-zen-of-just-writing-css.md b/apps/svelte.dev/content/blog/2017-09-06-the-zen-of-just-writing-css.md index f06a4aaac0..70e4cc06b9 100644 --- a/apps/svelte.dev/content/blog/2017-09-06-the-zen-of-just-writing-css.md +++ b/apps/svelte.dev/content/blog/2017-09-06-the-zen-of-just-writing-css.md @@ -19,7 +19,7 @@ Everything in CSS is global. Because of that, styles intended for one bit of mar It gets worse when you're working on a team. No-one dares touch styles authored by someone else, because it's often unclear what they're doing, what markup they apply to, and what disasters will unfold if you remove them. -The consequence of all this is the **append-only stylesheet**. There's no way of knowing which code can safely be removed, so it's common to undo some existing style with another, more specific style — even on relatively small projects. +The consequence of all this is the **append-only stylesheet**. There's no way of knowing which code can safely be removed, so it's common to undo some existing style with another, more specific style — even on relatively small projects. ## Single File Components change all that diff --git a/apps/svelte.dev/content/blog/2019-04-20-write-less-code.md b/apps/svelte.dev/content/blog/2019-04-20-write-less-code.md index 27a8e88c8c..86bcc083ce 100644 --- a/apps/svelte.dev/content/blog/2019-04-20-write-less-code.md +++ b/apps/svelte.dev/content/blog/2019-04-20-write-less-code.md @@ -110,7 +110,7 @@ It's unusual for the difference to be _quite_ so obvious — in my experience, a ### Top-level elements -In Svelte, a component can have as many top-level elements as you like. In React and Vue, a component must have a single top-level element — in React's case, trying to return two top-level elements from a component function would result in syntactically invalid code. (You can use a fragment — `<>` — instead of a `
`, but it's the same basic idea, and still results in an extra level of indentation). +In Svelte, a component can have as many top-level elements as you like. In React and Vue, a component must have a single top-level element — in React's case, trying to return two top-level elements from a component function would result in syntactically invalid code. (You can use a fragment — `<>` — instead of a `
`, but it's the same basic idea, and still results in an extra level of indentation). In Vue, your markup must be wrapped in a `