add more community libs and minor fixes

Author: vonovak

docs/community-libraries-and-navigators.md

@@ -14,18 +14,9 @@ A Shared Element Transition is the visualization of an element in one screen bei
 
 The library implements a custom navigator called `FluidNavigator` that makes all this and more possible. 
 
-### Installation
+#### Links
 
-Install the FluidTransitions package in your project:
-
-```
-npm install react-navigation-fluid-transitions
-yarn add react-navigation-fluid-transitions
-```
-
-### Links
-
-[https://github.com/fram-x/FluidTransitions](https://github.com/fram-x/FluidTransitions)
+[github.com/fram-x/FluidTransitions](https://github.com/fram-x/FluidTransitions)
 
 # Libraries
 
@@ -35,21 +26,34 @@ react-navigation-collapsible is a library and a `Higher Order Component` that ad
 
 Since react-navigation's header is designed as `Animated` component. You can animate the header by passing `Animated.Value` from your `ScrollView` or `FlatList` to the header.
 
-### Installation
+#### Links
+
+[https://github.com/benevbright/react-navigation-collapsible](https://github.com/benevbright/react-navigation-collapsible)
+
+[Demo on Snack](https://snack.expo.io/@benevbright/react-navigation-collapsible)
+
+## react-native-screens
+
+This project aims to expose native navigation container components to React Native and React Navigation can integrate with it since version 2.14.0. Using `react-native-screens` brings several benefits, such as support for the ["reachability feature"](https://www.cnet.com/how-to/how-to-use-reachability-on-iphone-6-6-plus/) on iOS, and improved memory consumption on both platforms.
+
+#### Links
+
+[github.com/kmagiera/react-native-screens](https://github.com/kmagiera/react-native-screens)
+
+## react-navigation-header-buttons
+
+Helps you to render buttons in the navigation bar and handle the styling so you don't have to. It tries to mimic the appearance of native navbar buttons and attempts to offer a simple interface for you to interact with.
 
-Install the react-navigation-collapsible package in your project:
+#### Links
 
-```
-yarn add react-navigation-collapsible
-# or, if you use npm:
-npm install react-navigation-collapsible
-```
+[github.com/vonovak/react-navigation-header-buttons](https://github.com/vonovak/react-navigation-header-buttons)
 
-### Demo on Snack
+[Demo on expo](https://expo.io/@vonovak/navbar-buttons-demo)
 
-<a href="https://snack.expo.io/@benevbright/react-navigation-collapsible" target="blank" class="run-code-button">&rarr; Run demo</a>
+## react-navigation-props-mapper
 
+Provides simple HOCs that map react-navigation props to your screen components directly - ie. instead of `const user = this.props.navigation.getParam(activeUser, null)`, you'd write `const user = this.props.activeUser`.
 
-### Links
+#### Links
 
-[https://github.com/benevbright/react-navigation-collapsible](https://github.com/benevbright/react-navigation-collapsible)
+[github.com/vonovak/react-navigation-props-mapper](https://github.com/vonovak/react-navigation-props-mapper)

docs/limitations.md

@@ -55,4 +55,6 @@ We are able to offload animations to another thread using React Native's [Animat
 
 Some platform-specific behavior either cannot be implemented or has not yet been implemented in React Navigation.
 
-One example of this is the ["reachability" feature on iOS](https://www.cnet.com/how-to/how-to-use-reachability-on-iphone-6-6-plus/). When you toggle this feature, the app moves down towards the bottom of the screen so you can easily reach the navigation bar and other functionality near the top of the UI. When you navigate to another screen using the built-in iOS navigation API, the UI will jump back up to the top of the screen. As far as we know, it is not possible implement this feature in user space. A similar limitation applies for the peek & pop feature available on devices with 3D touch.
+Versions prior to 2.14.0 do not support the ["reachability feature" on iOS](https://www.cnet.com/how-to/how-to-use-reachability-on-iphone-6-6-plus/). When you toggle this feature, the app moves down towards the bottom of the screen so you can easily reach the navigation bar and other functionality near the top of the UI. When you navigate to another screen using the built-in iOS navigation API, the UI will jump back up to the top of the screen. React-navigation 2.14.0 and later supports this feature through integration with [react-native-screens](https://github.com/kmagiera/react-native-screens).
+
+React-navigation does not include support for the peek & pop feature available on devices with 3D touch.

docs/navigation-prop.md

@@ -177,7 +177,7 @@ class ProfileScreen extends React.Component {
 
 ### `setParams` - Make changes to route params
 
-Firing the `setParams` action allows a screen to change the params in the route, which is useful for updating the header buttons and title.
+Firing the `setParams` action allows a screen to change the params in the route, which is useful for updating the header buttons and title. `setParams` works like React's `setState` - it merges the provided params object with the current params.
 
 ```js
 class ProfileScreen extends React.Component {