fix bugs on landing page code, make the url an easter egg

Summary:
This is just improving a bit of lameness on the homepage - Devin pointed out the <>'s don't work within a Text tag, so I removed them, and someone else pointed out that nonexistent fake urls are suboptimal, so I improved that too.
Closes https://github.com/facebook/react-native/pull/8387

Differential Revision: D3479087

Pulled By: JoelMarcey

fbshipit-source-id: 45a2d21a9073b58b869e8b344550c28f849e0185
This commit is contained in:
Kevin Lacker 2016-06-23 18:19:27 -07:00 committed by Facebook Github Bot
parent c6b1ed649f
commit 1ffecb4b5f
1 changed files with 5 additions and 5 deletions

View File

@ -50,8 +50,8 @@ class WhyReactNativeIsSoGreat extends Component {
If you like React on the web, you'll like React Native.
</Text>
<Text>
You just use native components like '<View>' and '<Text>',
instead of web components like '<div>' and '<a>'.
You just use native components like 'View' and 'Text',
instead of web components like 'div' and 'span'.
</Text>
</View>
);
@ -72,12 +72,12 @@ class AwkwardScrollingImageWithText extends Component {
render() {
return (
<ScrollView>
<Image source={{uri: 'http://facebook.github.io/react/thats-amazing.png'}} />
<Image source={{uri: 'https://i.chzbgr.com/full/7345954048/h7E2C65F9/'}} />
<Text>
On iOS, a React Native '<ScrollView>' uses a native UIScrollView.
On iOS, a React Native ScrollView uses a native UIScrollView.
On Android, it uses a native ScrollView.
On iOS, a React Native '<Image>' uses a native UIImageView.
On iOS, a React Native Image uses a native UIImageView.
On Android, it uses a native ImageView.
React Native wraps the fundamental native components, giving you