Skip to content

Commit 2547d06

Browse files
Update headers.md
Fix typos: "...across many screen." -> "...across many screens." "objexct" -> "object"
1 parent ba560bb commit 2547d06

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/headers.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -105,7 +105,7 @@ There are a couple of things to notice here:
105105

106106
## Sharing common `navigationOptions` across screens
107107

108-
It is common to want to configure the header in a similar way across many screen. For example, your company brand color might be red and so you want the header background color to be red and tint color to be white. Conveniently, these are the colors we're using our running example, and you'll notice that when you navigate to the `DetailsScreen` the colors go back to the defaults. Wouldn't it be awful if we had to copy the `navigationOptions` header style properties from `HomeScreen` to `DetailsScreen`, and for every single screen component we use in our app? Thankfully, we do not. We can instead move the configuration up to the `StackNavigator`.
108+
It is common to want to configure the header in a similar way across many screens. For example, your company brand color might be red and so you want the header background color to be red and tint color to be white. Conveniently, these are the colors we're using our running example, and you'll notice that when you navigate to the `DetailsScreen` the colors go back to the defaults. Wouldn't it be awful if we had to copy the `navigationOptions` header style properties from `HomeScreen` to `DetailsScreen`, and for every single screen component we use in our app? Thankfully, we do not. We can instead move the configuration up to the `StackNavigator`.
109109

110110
```js
111111
class HomeScreen extends React.Component {
@@ -208,6 +208,6 @@ You can read the full list of available screen `navigationOptions` for screens i
208208
## Summary
209209

210210
- You can customize the header inside of the `navigationOptions` static property on your screen components. Read the full list of options [in the API reference](stack-navigator.html#navigationoptions-used-by-stacknavigator).
211-
- The `navigationOptions` static property can be an object or a function. When it is a function, it is provided with an objexct with the `navigation` prop, `screenProps`, and `navigationOptions` on it.
211+
- The `navigationOptions` static property can be an object or a function. When it is a function, it is provided with an object with the `navigation` prop, `screenProps`, and `navigationOptions` on it.
212212
- You can also specify shared `navigationOptions` in the `StackNavigator` configuration when you initialize it. The static property takes precedence over that configuration.
213-
- [Full source of what we have built so far](https://snack.expo.io/@react-navigation/custom-header-title-component).
213+
- [Full source of what we have built so far](https://snack.expo.io/@react-navigation/custom-header-title-component).

0 commit comments

Comments
 (0)