From 8eb384e4fe4e83742fb1a50c5a6cee8c583358ca Mon Sep 17 00:00:00 2001
From: Melih <100301016@student.beykent.edu.tr>
Date: Mon, 24 Apr 2017 21:22:37 +0300
Subject: [PATCH] Update Screen-Nav-Options.md (#1211)

* Update Screen-Nav-Options.md

* Apply some tweaks
---
 .../docs/guides/Screen-Nav-Options.md                 | 11 +++++++----
 1 file changed, 7 insertions(+), 4 deletions(-)

diff --git a/packages/react-navigation/docs/guides/Screen-Nav-Options.md b/packages/react-navigation/docs/guides/Screen-Nav-Options.md
index f244d8b0..7c6f6b6e 100644
--- a/packages/react-navigation/docs/guides/Screen-Nav-Options.md
+++ b/packages/react-navigation/docs/guides/Screen-Nav-Options.md
@@ -64,15 +64,18 @@ Imagine the following scenario:
 Your `TabNavigator` represents one of the screens in the app, and is nested within a top-level `StackNavigator`:
 
 ```
-StackNavigator:
-  - route1: A screen
-  - route2: A TabNavigator
+StackNavigator({
+  route1: { screen: RouteOne },
+  route2: { screen: MyTabNavigator },
+}, {
+  headerMode: 'screen',
+});
 ```
 
 Now, when `route2` is active, you would like to hide the header. It's easy to hide the header for `route1`, and it should also be easy to do it for `route2`. This is what Default Navigation Options are for - they are simply `navigationOptions` set on a navigator:
 
 ```js
-TabNavigator({
+const MyTabNavigator = TabNavigator({
   profile: ProfileScreen,
   ...
 }, {