fix assets links

commit-id:1da21864

docs/index.md

@@ -1,4 +1,4 @@
-![logo](../assets/git_spr_logo.png)
+![logo](git_spr_logo.png)
 ## Stacked Pull Requests on GitHub
 
 I am a total practitioner of writing code in small consumable chunks, getting them reviewed and merged quickly. This approach leads to very fast paced code iterations, merge a lot and merge often. There is no question in my mind that writing software in this way is more productive than long lived branches with pull requests taking days or weeks to merge.
@@ -11,7 +11,7 @@ With SPR each git commit is an atomic unit of work that needs to pass all the ch
 
 SPR is a client side script integrated into git, there is no special configuration on GitHub or any special server side software that needs to run. It can be used in any GitHub repository and doesn't interfere with other workflows as it uses the same pull request model.
 
-![asciicasst](../assets/git_spr_cast.gif)
+![asciicasst](git_spr_cast.gif)
 --------------------------------------
 
 To create a pull request. Just commit your changes and call spr update. The branch is pushed to GitHub, and a pull request is created. 

readme.md

@@ -1,4 +1,4 @@
-![logo](assets/git_spr_logo.png)
+![logo](docs/git_spr_logo.png)
 # Stacked Pull Requests on GitHub
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
 [![Build](https://github.com/ejoffe/spr/actions/workflows/go_build.yml/badge.svg)](https://github.com/ejoffe/spr/actions/workflows/go_build.yml)
@@ -7,7 +7,7 @@
 [![Release](https://img.shields.io/github/release/ejoffe/spr.svg)](https://GitHub.com/ejoffe/spr/releases/) 
 [![Join the chat at https://gitter.im/ejoffe-spr/community](https://badges.gitter.im/ejoffe-spr/community.svg)](https://gitter.im/ejoffe-spr/community?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
 
-![asciicasst](assets/git_spr_cast.gif)
+![asciicasst](docs/git_spr_cast.gif)
 
 What is Stacked Diff Workflow?
 ------------------------------