From dbea88eede13f5085ee7d3b0c2bb2e6a886dce83 Mon Sep 17 00:00:00 2001 From: Prayag Verma Date: Mon, 13 Feb 2017 20:39:00 +0530 Subject: [PATCH] Fix a typo in design principles doc (#8985) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit unambigious → unambiguous --- contributing/design-principles.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/contributing/design-principles.md b/contributing/design-principles.md index 2c5064a5..3e848df3 100644 --- a/contributing/design-principles.md +++ b/contributing/design-principles.md @@ -146,7 +146,7 @@ Optimizing for search is also important because of our reliance on [codemods](ht [JSX](/react/docs/displaying-data.html#jsx-syntax) plays a similar role. While it is not required with React, we use it extensively at Facebook both for aesthetic and pragmatic reasons. -In our codebase, JSX provides an unambigious hint to the tools that they are dealing with a React element tree. This makes it possible to add build-time optimizations such as [hoisting constant elements](http://babeljs.io/docs/plugins/transform-react-constant-elements/), safely lint and codemod internal component usage, and [include JSX source location](https://github.com/facebook/react/pull/6771) into the warnings. +In our codebase, JSX provides an unambiguous hint to the tools that they are dealing with a React element tree. This makes it possible to add build-time optimizations such as [hoisting constant elements](http://babeljs.io/docs/plugins/transform-react-constant-elements/), safely lint and codemod internal component usage, and [include JSX source location](https://github.com/facebook/react/pull/6771) into the warnings. ### Dogfooding