Updated path to syntax highlighting example image for SGK gitweb server.

[vvhitespace] / syntax_highlighting / README.md

diff --git a/syntax_highlighting/README.md b/syntax_highlighting/README.md
index 0228471..71718a2 100644 (file)
--- a/syntax_highlighting/README.md
+++ b/syntax_highlighting/README.md
@@ -1,7 +1,7 @@
 VVhitespace Syntax Highlighting
 ===============================
 
 VVhitespace Syntax Highlighting
 ===============================
 

-![VVS Syntax Highlighting Example](vvs_syntax_highlighting.gif)
+![VVS Syntax Highlighting Example](/vvhitespace/.git/blob_plain/HEAD:/syntax_highlighting/vvs_syntax_highlighting.gif)

 
 I find it useful to highlight each IMP a different color as well as highlight
 code comments and label definitions. The above image is typical of my
 
 I find it useful to highlight each IMP a different color as well as highlight
 code comments and label definitions. The above image is typical of my


@@ -39,7 +39,7 @@ Create a file named `~/.vim/syntax/vvhitespace.vim` containing the following:
       finish
     endif
     
       finish
     endif
     

-    let b:current_synax = "vvhitespace"
+    let b:current_syntax = "vvhitespace"

     
     " Stack IMP
     syn match stackIMP '^[sS][sS]'
     
     " Stack IMP
     syn match stackIMP '^[sS][sS]'


@@ -77,7 +77,7 @@ Create a file named `~/.vim/syntax/vvhitespace.vim` containing the following:
 That's it! You should now see syntax highlighting when opening files with names
 ending in `*.pvvs`.
 
 That's it! You should now see syntax highlighting when opening files with names
 ending in `*.pvvs`.
 

-If you don't any see syntax highlighting, check your `.vimrc` and other config
+If you don't see any syntax highlighting, check your `.vimrc` and other config

 locations for conflicting options. Try manually enabling syntax highlighting
 with the `syntax on` configuration directive.
 
 locations for conflicting options. Try manually enabling syntax highlighting
 with the `syntax on` configuration directive.