Fix a typo in design principles doc (#8985)
unambigious → unambiguous
Prayag Verma committed
Feb 13, 2017 at 20:39 UTC
c60f852cdbb9f115264537d39e2aedea6c1c9636
1 file changed
+1
-1
docs/contributing/design-principles.md
+1
-1
@@ -146,7 +146,7 @@ Optimizing for search is also important because of our reliance on [codemods](ht
146
147
[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.
148
149
-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.
149
+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.
150
151
### Dogfooding
152