move gitcasts videos to be embedded at top of the screen

Author: brntbeer

p/branching.md

@@ -4,6 +4,8 @@ title: Branching and Merging
 description: Create and work on topic and long running branches, merge between them and delete them.
 ---
 
+<center><embed src="http://www.youtube.com/v/tl5IDfwdvxo" type="application/x-shockwave-flash" width="790" height="430" allowscriptaccess="always" allowfullscreen="true"></embed></center>
+
 As we touched on in the first lesson, the way that Git handles branching and
 merging is pretty unique.  First of all, it's incredibly fast, both to create
 new branches and to switch between them. Git has a single working directory

p/log.md

@@ -4,6 +4,8 @@ title: Git History
 description: Browse your project history, find specific commits, and visualize the branching and merging actions.
 ---
 
+<center><embed src="http://www.youtube.com/v/jnGbU-_m8oY" type="application/x-shockwave-flash" width="790" height="430" allowscriptaccess="always" allowfullscreen="true"></embed></center>
+
 One of the most commonly used commands is the 'git log' command.  This command
 shows you the commit history of your project, so you can see what has happened
 up to this point.  With no options, it will start from the last commit on

p/normal.md

@@ -4,6 +4,8 @@ title: Normal Workflow
 description: Make and view changes made, then stage and commit them.
 ---
 
+<center><embed src="http://www.youtube.com/v/U1ayH6KLqxo" type="application/x-shockwave-flash" width="790" height="430" allowscriptaccess="always" allowfullscreen="true"></embed></center>
+
 So you have a Git repository and everything is all setup.  What now?
 
 Generally, it is not going to be much different than working with any other

p/rebasing.md

@@ -4,6 +4,8 @@ title: Rebasing
 description: Replay changes from one branch onto another branch to preserve a linear history.
 ---
 
+<center><embed src="http://www.youtube.com/v/FyxiLdelSqc" type="application/x-shockwave-flash" width="790" height="430" allowscriptaccess="always" allowfullscreen="true"></embed></center>
+
 In Git, there are two main ways to integrate changes from one branch into
 another - the 'merge' and the 'rebase'.  In this section we will learn what
 'rebasing' is, how to do it and in what cases it may not be a good idea to.

p/remotes.md

@@ -3,6 +3,9 @@ layout: default
 title: Distributed Git
 description: Fetch, merge, pull, and push between multiple remote repositories.
 ---
+
+<center><embed src="http://www.youtube.com/v/KWNIKb6sftw" type="application/x-shockwave-flash" width="790" height="430" allowscriptaccess="always" allowfullscreen="true"></embed></center>
+
 So you've heard that Git is a **distributed** version control system.  What
 does that really mean and how do you take advantage of it?
 

p/setup.md

@@ -4,6 +4,8 @@ title: Setup and Initialization
 description: Setup your Git environment, then create a new Git repository and clone an existing one.
 ---
 
+<center><embed src="http://www.youtube.com/v/Esl439M154M" type="application/x-shockwave-flash" width="790" height="430" allowscriptaccess="always" allowfullscreen="true"></embed></center>
+
 ### setting up git
 
 When you first start using Git, there are a few things you will likely want