From df50aea37872ac1de40052ca9cc00267821f92d3 Mon Sep 17 00:00:00 2001
From: Dorell James <galangdj@gmail.com>
Date: Fri, 25 Oct 2019 12:04:28 +0800
Subject: [PATCH] Update working-with-video.md

Fixes Video component file.
---
 docs/docs/working-with-video.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/docs/docs/working-with-video.md b/docs/docs/working-with-video.md
index 857f1665c8f7a..54b95ab047f6b 100644
--- a/docs/docs/working-with-video.md
+++ b/docs/docs/working-with-video.md
@@ -23,7 +23,8 @@ If you would like more control over how YouTube (or similar) videos are embedded
 
 In this reusable sample component, you could include props for video data like URL or title, any necessary markup for styling purposes, and the common `iframe` embed code:
 
-```js:title=components/video.js
+```jsx:title=src/components/video.js
+import React from "react"
 const Video = ({ videoSrcURL, videoTitle, ...props }) => (
   <div className="video">
     <iframe
@@ -37,6 +38,7 @@ const Video = ({ videoSrcURL, videoTitle, ...props }) => (
     />
   </div>
 )
+export default Video
 ```
 
 You would then include this component in a template or page with a video source URL and title passed in as props. The data for video URLs and titles can be sourced in multiple ways, such as importing JSON or [querying data from Markdown with GraphQL](#querying-data-from-markdown-with-graphql). You can also hard-code video data for something fun, like a custom 404 page with an Easter egg YouTube video: