Sync changes to unversioned docs

hramos · hramos · commit d205cadb1beb · 2018-07-03T10:11:34.000-07:00
diff --git a/website/versioned_docs/version-0.5/javascript-environment.md b/website/versioned_docs/version-0.5/javascript-environment.md
@@ -61,7 +61,7 @@ Many standards functions are also available on all the supported JavaScript runt
 
 Browser
 
-* [console.{log, warn, error, info, trace, table}](https://developer.chrome.com/devtools/docs/console-api)
+* [console.{log, warn, error, info, trace, table, group, groupEnd}](https://developer.chrome.com/devtools/docs/console-api)
 * [CommonJS require](https://nodejs.org/docs/latest/api/modules.html)
 * [XMLHttpRequest, fetch](network.md#content)
 * [{set, clear}{Timeout, Interval, Immediate}, {request, cancel}AnimationFrame](timers.md#content)
diff --git a/website/versioned_docs/version-0.5/navigation.md b/website/versioned_docs/version-0.5/navigation.md
@@ -33,6 +33,8 @@ const App = createStackNavigator({
   Home: { screen: HomeScreen },
   Profile: { screen: ProfileScreen },
 });
+
+export default App;
 ```
 
 Each screen component can set navigation options such as the header title. It can use action creators on the `navigation` prop to link to other screens:
diff --git a/website/versioned_docs/version-0.5/performance.md b/website/versioned_docs/version-0.5/performance.md
@@ -484,7 +484,7 @@ fs.writeFile('./packager/modulePaths.js', fileData, err => {
 });
 ```
 
-You can run via `node packager/modulePaths.js`.
+You can run via `node packager/generateModulePaths.js`.
 
 This script attempts to map from the module names to module paths. Its not foolproof though, for instance, it ignores platform specific files (\*ios.js, and \*.android.js). However based on initial testing, it handles 95% of cases. When it runs, after some time it should complete and output a file named `packager/modulePaths.js`. It should contain paths to module files that are relative to your projects root. You can commit modulePaths.js to your repo so it is transportable.
 
diff --git a/website/versioned_docs/version-0.5/state.md b/website/versioned_docs/version-0.5/state.md
@@ -52,7 +52,7 @@ export default class BlinkApp extends Component {
 AppRegistry.registerComponent('AwesomeProject', () => BlinkApp);
 ```
 
-In a real application, you probably won't be setting state with a timer. You might set state when you have new data arrived from the server, or from user input. You can also use a state container like [Redux](https://redux.js.org/) to control your data flow. In that case you would use Redux to modify your state rather than calling `setState` directly.
+In a real application, you probably won't be setting state with a timer. You might set state when you have new data arrived from the server, or from user input. You can also use a state container like [Redux](https://redux.js.org/) or [Mobx](https://mobx.js.org/) to control your data flow. In that case you would use Redux or Mobx to modify your state rather than calling `setState` directly.
 
 When setState is called, BlinkApp will re-render its Component. By calling setState within the Timer, the component will re-render every time the Timer ticks.
 
