{"files":[{"status":"M","path":"docs\/_posts\/2013-06-12-community-roundup.md"},{"status":"M","path":"docs\/_posts\/2013-06-19-community-roundup-2.md"},{"status":"M","path":"docs\/_posts\/2013-06-27-community-roundup-3.md"},{"status":"M","path":"docs\/_posts\/2013-09-24-community-roundup-8.md"},{"status":"M","path":"docs\/_posts\/2013-12-23-community-roundup-12.md"},{"status":"M","path":"docs\/_posts\/2013-12-30-community-roundup-13.md"},{"status":"M","path":"docs\/_posts\/2014-02-05-community-roundup-15.md"},{"status":"M","path":"docs\/_posts\/2014-02-15-community-roundup-16.md"},{"status":"M","path":"docs\/_posts\/2014-08-03-community-roundup-21.md"},{"status":"M","path":"docs\/_posts\/2015-02-18-react-conf-roundup-2015.md"},{"status":"M","path":"docs\/community\/videos.it-IT.md"},{"status":"M","path":"docs\/docs\/lists-and-keys.md"}],"patch":"diff --git a\/docs\/_posts\/2013-06-12-community-roundup.md b\/docs\/_posts\/2013-06-12-community-roundup.md\nindex b1a57a51d1..ebe082c283 100644\n--- a\/docs\/_posts\/2013-06-12-community-roundup.md\n+++ b\/docs\/_posts\/2013-06-12-community-roundup.md\n@@ -32,7 +32,7 @@ It looks like [Ben Alpert](http:\/\/benalpert.com\/) is the first person outside of\n \n [Mario Mueller](http:\/\/blog.xenji.com\/) wrote a menu component in React and was able to easily integrate it with require.js, EventEmitter2 and bower.\n \n-> I recently stumbled upon facebook's React library, which is a Javascript library for building reusable frontend components. Even if this lib is only at version 0.3.x it behaves very stable, it is fast and is fun to code. I'm a big fan of require.js, so I tried to use React within the require.js eco system. It was not as hard as expected and here are some examples and some thoughts about it.\n+> I recently stumbled upon facebook's React library, which is a JavaScript library for building reusable frontend components. Even if this lib is only at version 0.3.x it behaves very stable, it is fast and is fun to code. I'm a big fan of require.js, so I tried to use React within the require.js eco system. It was not as hard as expected and here are some examples and some thoughts about it.\n >\n > [Read the full post...](http:\/\/blog.xenji.com\/2013\/06\/facebooks-react-require-js.html)\n \n@@ -40,7 +40,7 @@ It looks like [Ben Alpert](http:\/\/benalpert.com\/) is the first person outside of\n \n [Pete Hunt](http:\/\/www.petehunt.net\/blog\/) explained what differentiates React from other JavaScript libraries in [a previous blog post](\/react\/blog\/2013\/06\/05\/why-react.html). [Lee Byron](http:\/\/leebyron.com\/) gives another perspective on Quora:\n \n-> React isn't quite like any other popular Javascript libraries, and it solves a very specific problem: complex UI rendering. It's also intended to be used along side many other popular libraries. For example, React works well with Backbone.js, amongst many others.\n+> React isn't quite like any other popular JavaScript libraries, and it solves a very specific problem: complex UI rendering. It's also intended to be used along side many other popular libraries. For example, React works well with Backbone.js, amongst many others.\n >\n > React was born out of frustrations with the common pattern of writing two-way data bindings in complex MVC apps. React is an implementation of one-way data bindings.\n >\ndiff --git a\/docs\/_posts\/2013-06-19-community-roundup-2.md b\/docs\/_posts\/2013-06-19-community-roundup-2.md\nindex 1de3fe34f9..3ac7f9b796 100644\n--- a\/docs\/_posts\/2013-06-19-community-roundup-2.md\n+++ b\/docs\/_posts\/2013-06-19-community-roundup-2.md\n@@ -9,7 +9,7 @@ Since the launch we have received a lot of feedback and are actively working on\n \n [Andrew Greig](http:\/\/www.andrewgreig.com\/) made a blog post that gives a high level description of what React is.\n \n-> I have been using Facebooks recently released Javascript framework called React.js for the last few days and have managed to obtain a rather high level understanding of how it works and formed a good perspective on how it fits in to the entire javascript framework ecosystem.\n+> I have been using Facebooks recently released JavaScript framework called React.js for the last few days and have managed to obtain a rather high level understanding of how it works and formed a good perspective on how it fits in to the entire javascript framework ecosystem.\n >\n > Basically, React is not an MVC framework. It is not a replacement for Backbone or Knockout or Angular, instead it is designed to work with existing frameworks and help extend their functionality.\n >\ndiff --git a\/docs\/_posts\/2013-06-27-community-roundup-3.md b\/docs\/_posts\/2013-06-27-community-roundup-3.md\nindex d46d490b84..b2a221c1f8 100644\n--- a\/docs\/_posts\/2013-06-27-community-roundup-3.md\n+++ b\/docs\/_posts\/2013-06-27-community-roundup-3.md\n@@ -19,7 +19,7 @@ The highlight of this week is that an interaction-heavy app has been ported to R\n \n ## Grunt Task for JSX\n \n-[Eric Clemmons](https:\/\/ericclemmons.github.io\/) wrote a task for [Grunt](http:\/\/gruntjs.com\/) that applies the JSX transformation to your Javascript files. It also works with [Browserify](http:\/\/browserify.org\/) if you want all your files to be concatenated and minified together.\n+[Eric Clemmons](https:\/\/ericclemmons.github.io\/) wrote a task for [Grunt](http:\/\/gruntjs.com\/) that applies the JSX transformation to your JavaScript files. It also works with [Browserify](http:\/\/browserify.org\/) if you want all your files to be concatenated and minified together.\n \n > Grunt task for compiling Facebook React's .jsx templates into .js\n >\n@@ -81,9 +81,9 @@ browserify: {\n >\n > [Read the full post...](http:\/\/blog.vjeux.com\/2013\/javascript\/react-coffeescript.html)\n \n-## Tutorial in Plain Javascript\n+## Tutorial in Plain JavaScript\n \n-We've seen a lot of people comparing React with various frameworks. [Ricardo Tomasi](http:\/\/ricardo.cc\/) decided to re-implement the tutorial without any framework, just plain Javascript.\n+We've seen a lot of people comparing React with various frameworks. [Ricardo Tomasi](http:\/\/ricardo.cc\/) decided to re-implement the tutorial without any framework, just plain JavaScript.\n \n > Facebook & Instagram launched the React framework and an accompanying tutorial. Developer Vlad Yazhbin decided to rewrite that using AngularJS. The end result is pretty neat, but if you're like me you will not actually appreciate the HTML speaking for itself and doing all the hard work. So let's see what that looks like in plain javascript.\n >\ndiff --git a\/docs\/_posts\/2013-09-24-community-roundup-8.md b\/docs\/_posts\/2013-09-24-community-roundup-8.md\nindex 3f75ece689..f3189042f2 100644\n--- a\/docs\/_posts\/2013-09-24-community-roundup-8.md\n+++ b\/docs\/_posts\/2013-09-24-community-roundup-8.md\n@@ -9,9 +9,9 @@ First, we are organizing a [React Hackathon](http:\/\/reactjshack-a-thon.splashtha\n \n We've also reached a point where there are too many questions for us to handle directly. We're encouraging people to ask questions on [StackOverflow](http:\/\/stackoverflow.com\/questions\/tagged\/reactjs) using the tag [[reactjs]](http:\/\/stackoverflow.com\/questions\/tagged\/reactjs). Many members of the team and community have subscribed to the tag, so feel free to ask questions there. We think these will be more discoverable than Google Groups archives or IRC logs.\n \n-## Javascript Jabber\n+## JavaScript Jabber\n \n-[Pete Hunt](http:\/\/www.petehunt.net\/) and [Jordan Walke](https:\/\/github.com\/jordwalke) were interviewed on [Javascript Jabber](http:\/\/javascriptjabber.com\/073-jsj-react-with-pete-hunt-and-jordan-walke\/) for an hour. They go over many aspects of React such as 60 FPS, Data binding, Performance, Diffing Algorithm, DOM Manipulation, Node.js support, server-side rendering, JSX, requestAnimationFrame and the community. This is a gold mine of information about React.\n+[Pete Hunt](http:\/\/www.petehunt.net\/) and [Jordan Walke](https:\/\/github.com\/jordwalke) were interviewed on [JavaScript Jabber](http:\/\/javascriptjabber.com\/073-jsj-react-with-pete-hunt-and-jordan-walke\/) for an hour. They go over many aspects of React such as 60 FPS, Data binding, Performance, Diffing Algorithm, DOM Manipulation, Node.js support, server-side rendering, JSX, requestAnimationFrame and the community. This is a gold mine of information about React.\n \n > **PETE:** So React was designed all around that. Conceptually, how you build a React app is that every time your data changes, it's like hitting the refresh button in a server-rendered app. What we do is we conceptually throw out all of the markup and event handlers that you've registered and we reset the whole page and then we redraw the entire page. If you're writing a server-rendered app, handling updates is really easy because you hit the refresh button and you're pretty much guaranteed to get what you expect.\n >\n@@ -53,7 +53,7 @@ While this is not going to work for all the attributes since they are camelCased\n \n ## Markdown in React\n \n-[Ben Alpert](http:\/\/benalpert.com\/) converted [marked](https:\/\/github.com\/chjj\/marked), a Markdown Javascript implementation, in React: [marked-react](https:\/\/github.com\/spicyj\/marked-react). Even without using JSX, the HTML generation is now a lot cleaner. It is also safer as forgetting a call to `escape` will not introduce an XSS vulnerability.\n+[Ben Alpert](http:\/\/benalpert.com\/) converted [marked](https:\/\/github.com\/chjj\/marked), a Markdown JavaScript implementation, in React: [marked-react](https:\/\/github.com\/spicyj\/marked-react). Even without using JSX, the HTML generation is now a lot cleaner. It is also safer as forgetting a call to `escape` will not introduce an XSS vulnerability.\n

[![](\/react\/img\/blog\/markdown_refactor.png)](https:\/\/github.com\/spicyj\/marked-react\/commit\/cb70c9df6542c7c34ede9efe16f9b6580692a457)<\/figure>\n \n \ndiff --git a\/docs\/_posts\/2013-12-23-community-roundup-12.md b\/docs\/_posts\/2013-12-23-community-roundup-12.md\nindex 55bf87a650..8c5cd25b03 100644\n--- a\/docs\/_posts\/2013-12-23-community-roundup-12.md\n+++ b\/docs\/_posts\/2013-12-23-community-roundup-12.md\n@@ -5,7 +5,7 @@ author: vjeux\n \n React got featured on the front-page of Hacker News thanks to the Om library. If you try it out for the first time, take a look at the [docs](\/react\/docs\/getting-started.html) and do not hesitate to ask questions on the [Google Group](https:\/\/groups.google.com\/group\/reactjs), [IRC](irc:\/\/chat.freenode.net\/reactjs) or [Stack Overflow](http:\/\/stackoverflow.com\/questions\/tagged\/reactjs). We are trying our best to help you out!\n \n-## The Future of Javascript MVC\n+## The Future of JavaScript MVC\n \n [David Nolen](https:\/\/swannodette.github.io\/) announced Om, a thin wrapper on-top of React in ClojureScript. It stands out by only using immutable data structures. This unlocks the ability to write a very efficient [shouldComponentUpdate](\/react\/docs\/component-specs.html#updating-shouldcomponentupdate) and get huge performance improvements on some tasks.\n \ndiff --git a\/docs\/_posts\/2013-12-30-community-roundup-13.md b\/docs\/_posts\/2013-12-30-community-roundup-13.md\nindex a489bb604b..2acf62ea5c 100644\n--- a\/docs\/_posts\/2013-12-30-community-roundup-13.md\n+++ b\/docs\/_posts\/2013-12-30-community-roundup-13.md\n@@ -26,11 +26,11 @@ Happy holidays! This blog post is a little-late Christmas present for all the Re\n \n JSX is often compared to the now defunct E4X, [Vjeux](http:\/\/blog.vjeux.com\/) went over all the E4X features and explained how JSX is different and hopefully doesn't repeat the same mistakes.\n \n-> E4X (ECMAScript for XML) is a Javascript syntax extension and a runtime to manipulate XML. It was promoted by Mozilla but failed to become mainstream and is now deprecated. JSX was inspired by E4X. In this article, I'm going to go over all the features of E4X and explain the design decisions behind JSX.\n+> E4X (ECMAScript for XML) is a JavaScript syntax extension and a runtime to manipulate XML. It was promoted by Mozilla but failed to become mainstream and is now deprecated. JSX was inspired by E4X. In this article, I'm going to go over all the features of E4X and explain the design decisions behind JSX.\n >\n > **Historical Context**\n >\n-> E4X has been created in 2002 by John Schneider. This was the golden age of XML where it was being used for everything: data, configuration files, code, interfaces (DOM) ... E4X was first implemented inside of Rhino, a Javascript implementation from Mozilla written in Java.\n+> E4X has been created in 2002 by John Schneider. This was the golden age of XML where it was being used for everything: data, configuration files, code, interfaces (DOM) ... E4X was first implemented inside of Rhino, a JavaScript implementation from Mozilla written in Java.\n >\n > [Continue reading ...](http:\/\/blog.vjeux.com\/2013\/javascript\/jsx-e4x-the-good-parts.html)\n \ndiff --git a\/docs\/_posts\/2014-02-05-community-roundup-15.md b\/docs\/_posts\/2014-02-05-community-roundup-15.md\nindex ae6f3c7ceb..2e702f633c 100644\n--- a\/docs\/_posts\/2014-02-05-community-roundup-15.md\n+++ b\/docs\/_posts\/2014-02-05-community-roundup-15.md\n@@ -3,7 +3,7 @@ title: \"Community Round-up #15\"\n author: jgebhardt\n ---\n \n-Interest in React seems to have surged ever since David Nolen ([@swannodette](https:\/\/twitter.com\/swannodette))'s introduction of [Om](https:\/\/github.com\/swannodette\/om) in his post [\"The Future of Javascript MVC Frameworks\"](https:\/\/swannodette.github.io\/2013\/12\/17\/the-future-of-javascript-mvcs\/).\n+Interest in React seems to have surged ever since David Nolen ([@swannodette](https:\/\/twitter.com\/swannodette))'s introduction of [Om](https:\/\/github.com\/swannodette\/om) in his post [\"The Future of JavaScript MVC Frameworks\"](https:\/\/swannodette.github.io\/2013\/12\/17\/the-future-of-javascript-mvcs\/).\n \n In this React Community Round-up, we are taking a closer look at React from a functional programming perspective.\n \ndiff --git a\/docs\/_posts\/2014-02-15-community-roundup-16.md b\/docs\/_posts\/2014-02-15-community-roundup-16.md\nindex 69fab70dda..7bb30864ae 100644\n--- a\/docs\/_posts\/2014-02-15-community-roundup-16.md\n+++ b\/docs\/_posts\/2014-02-15-community-roundup-16.md\n@@ -60,7 +60,7 @@ Joe Maddalone ([@joemaddalone](https:\/\/twitter.com\/joemaddalone)) of [egghead.io\n \n Eric Florenzano ([@ericflo](https:\/\/twitter.com\/ericflo)) sheds some light on what makes React perfect for server rendering:\n \n-> [...] the ideal solution would fully render the markup on the server, deliver it to the client so that it can be shown to the user instantly. Then it would asynchronously load some Javascript that would attach to the rendered markup, and invisibly promote the page into a full app that can render its own markup. [...]\n+> [...] the ideal solution would fully render the markup on the server, deliver it to the client so that it can be shown to the user instantly. Then it would asynchronously load some JavaScript that would attach to the rendered markup, and invisibly promote the page into a full app that can render its own markup. [...]\n \n > What I've discovered is that enough of the pieces have come together, that this futuristic-sounding web environment is actually surprisingly easy to do now with React.js.\n \ndiff --git a\/docs\/_posts\/2014-08-03-community-roundup-21.md b\/docs\/_posts\/2014-08-03-community-roundup-21.md\nindex 9ed6f9d6ed..7a310cd3d0 100644\n--- a\/docs\/_posts\/2014-08-03-community-roundup-21.md\n+++ b\/docs\/_posts\/2014-08-03-community-roundup-21.md\n@@ -21,7 +21,7 @@ React.renderComponent((\n \n ## Going Big with React\n \n-Areeb Malik, from Facebook, talks about his experience using React. \"On paper, all those JS frameworks look promising: clean implementations, quick code design, flawless execution. But what happens when you stress test Javascript? What happens when you throw 6 megabytes of code at it? In this talk, we'll investigate how React performs in a high stress situation, and how it has helped our team build safe code on a massive scale\"\n+Areeb Malik, from Facebook, talks about his experience using React. \"On paper, all those JS frameworks look promising: clean implementations, quick code design, flawless execution. But what happens when you stress test JavaScript? What happens when you throw 6 megabytes of code at it? In this talk, we'll investigate how React performs in a high stress situation, and how it has helped our team build safe code on a massive scale\"\n \n [![](\/react\/img\/blog\/skills-matter.png)](https:\/\/skillsmatter.com\/skillscasts\/5429-going-big-with-react)\n \n@@ -32,7 +32,7 @@ Areeb Malik, from Facebook, talks about his experience using React. \"On paper, a\n \n ## What is React?\n \n-[Craig McKeachie](http:\/\/www.funnyant.com\/author\/admin\/) author of [Javascript Framework Guide](http:\/\/www.funnyant.com\/javascript-framework-guide\/) wrote an excellent news named [\"What is React.js? Another Template Library?](http:\/\/www.funnyant.com\/reactjs-what-is-it\/)\n+[Craig McKeachie](http:\/\/www.funnyant.com\/author\/admin\/) author of [JavaScript Framework Guide](http:\/\/www.funnyant.com\/javascript-framework-guide\/) wrote an excellent news named [\"What is React.js? Another Template Library?](http:\/\/www.funnyant.com\/reactjs-what-is-it\/)\n \n - Is React a template library?\n - Is React similar to Web Components?\ndiff --git a\/docs\/_posts\/2015-02-18-react-conf-roundup-2015.md b\/docs\/_posts\/2015-02-18-react-conf-roundup-2015.md\nindex 447e9b84f0..72fefbaabf 100644\n--- a\/docs\/_posts\/2015-02-18-react-conf-roundup-2015.md\n+++ b\/docs\/_posts\/2015-02-18-react-conf-roundup-2015.md\n@@ -156,7 +156,7 @@ It was a privilege to welcome the React community to Facebook HQ on January 28\n

<\/a>Immutability #<\/a><\/h3>\n
\n- Lee Byron<\/strong> led a master-class on persistent immutable data structures, showing us the world of possibility that they can unlock for your software, and perhaps Javascript in general.\n+ Lee Byron<\/strong> led a master-class on persistent immutable data structures, showing us the world of possibility that they can unlock for your software, and perhaps JavaScript in general.\n <\/p>\n <\/div>\n
\ndiff --git a\/docs\/community\/videos.it-IT.md b\/docs\/community\/videos.it-IT.md\nindex 814e70ccf3..099024506e 100644\n--- a\/docs\/community\/videos.it-IT.md\n+++ b\/docs\/community\/videos.it-IT.md\n@@ -31,7 +31,7 @@ Un video di [tagtree.tv](http:\/\/tagtree.tv\/) che espone i principi di [Pensare i\n \n ### Pensare in grande con React\n \n-\"Sulla carta, tutti questi framework JS sembrano promettenti: implementazioni pulite, design veloce del codice, esecuzione perfetta. Ma che succede quando metti Javascript sotto stress? Che succede se gli dài in pasto 6 megabyte di codice? In questo talk investigheremo come si comporta React in situazioni di stress elevato, e come ha aiutato il nostro team a costruire codice sicuro ad una scala enorme.\"\n+\"Sulla carta, tutti questi framework JS sembrano promettenti: implementazioni pulite, design veloce del codice, esecuzione perfetta. Ma che succede quando metti JavaScript sotto stress? Che succede se gli dài in pasto 6 megabyte di codice? In questo talk investigheremo come si comporta React in situazioni di stress elevato, e come ha aiutato il nostro team a costruire codice sicuro ad una scala enorme.\"\n
[![](https:\/\/i.vimeocdn.com\/video\/481670116_650.jpg)](https:\/\/skillsmatter.com\/skillscasts\/5429-going-big-with-react#video)<\/figure>\n \n * * *\ndiff --git a\/docs\/docs\/lists-and-keys.md b\/docs\/docs\/lists-and-keys.md\nindex c2b1527087..9283fbe4ae 100644\n--- a\/docs\/docs\/lists-and-keys.md\n+++ b\/docs\/docs\/lists-and-keys.md\n@@ -24,7 +24,7 @@ In React, transforming arrays into lists of [elements](\/react\/docs\/rendering-ele\n \n You can build collections of elements and [include them in JSX](\/react\/docs\/introducing-jsx.html#embedding-expressions-in-jsx) using curly braces `{}`.\n \n-Below, we loop through the `numbers` array using the Javascript [`map()`](https:\/\/developer.mozilla.org\/en-US\/docs\/Web\/JavaScript\/Reference\/Global_Objects\/Array\/map) function. We return an `
` element for each item. Finally, we assign the resulting array of elements to `listItems`:\n+Below, we loop through the `numbers` array using the JavaScript [`map()`](https:\/\/developer.mozilla.org\/en-US\/docs\/Web\/JavaScript\/Reference\/Global_Objects\/Array\/map) function. We return an `
` element for each item. Finally, we assign the resulting array of elements to `listItems`:\n \n ```javascript{2-4}\n const numbers = [1, 2, 3, 4, 5];\n","body":"","parents":["8ca82e1df6715ab10ea1bb0c1f9af9611c837a7e"],"commit":{"shortRevision":"b88c42d970","authorName":"Lipis","revision":"b88c42d9709b9fbfd7bb7ebf70bd57eb2b0d91f1","authorEmail":"lipiridis@gmail.com","authoredAt":"2017-05-31T04:35:22+02:00","subject":"Rename Javascript to JavaScript (#9796)"}}

dillon1000/react

Files changed