From 749622f43d664c3c3a5180e780eb8786ae959118 Mon Sep 17 00:00:00 2001 From: "Patrick H. Lauke" Date: Tue, 30 Jul 2019 07:42:55 +0100 Subject: [PATCH] Fix minor typo (#29168) --- site/content/docs/4.3/extend/approach.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/site/content/docs/4.3/extend/approach.md b/site/content/docs/4.3/extend/approach.md index 2ba15ef182..3c4d1dae84 100644 --- a/site/content/docs/4.3/extend/approach.md +++ b/site/content/docs/4.3/extend/approach.md @@ -61,7 +61,7 @@ Learn more about this in our [`z-index` layout page]({{< docsref "/layout/overvi Whenever possible, we prefer to write HTML and CSS over JavaScript. In general, HTML and CSS are more prolific and accessible to more people of all different experience levels. HTML and CSS are also faster in your browser than JavaScript, and your browser generally provides a great deal of functionality for you. -This principle is our first-class JavaScript API is `data` attributes. You don't need to write nearly any JavaScript to use our JavaScript plugins; instead, write HTML. Read more about this in [our JavaScript overview page]({{< docsref "/getting-started/javascript#data-attributes" >}}). +This principle is our first-class JavaScript API using `data` attributes. You don't need to write nearly any JavaScript to use our JavaScript plugins; instead, write HTML. Read more about this in [our JavaScript overview page]({{< docsref "/getting-started/javascript#data-attributes" >}}). Lastly, our styles build on the fundamental behaviors of common web elements. Whenever possible, we prefer to use what the browser provides. For example, you can put a `.btn` class on nearly any element, but most elements don't provide any semantic value or browser functionality. So instead, we use `