fixing git url on README, ref #17

diff --git a/README.md b/README.md
index df911d096ced7618b0740c8fc5406329915b6420..782a02d4f8f118c33154d2015429c52ae4c08442 100644 (file)
--- a/README.md
+++ b/README.md
@@ -157,8 +157,8 @@ You can start a new extension with git support calling `skeleton` task with
 `--git` flag, then in addition to create skeleton, `pgxn-utils` will initialize
 a git repository and do a initial commit.
 
-Once you have you extension in a git repository your `bundle` will use only the
-commited files to create the archive, but if your repository is dirty `pgxn-utils`
+Once you have your extension in a git repository your `bundle` will use only the
+commited files to create the archive, but if your repository is dirty then `pgxn-utils`
 will hint you to commit or stash your changes, before bundle.
 
 You must be careful with new files not added to repository, because they will NOT

diff --git a/Rakefile b/Rakefile
index f373afdb5e09724b5bbdf73dca18c92851f2c0e0..67f775a93f6a6e94e752a95b34384727436ad39b 100644 (file)
--- a/Rakefile
+++ b/Rakefile
@@ -106,8 +106,8 @@ You can start a new extension with git support calling `skeleton` task with
 `--git` flag, then in addition to create skeleton, `pgxn-utils` will initialize
 a git repository and do a initial commit.
 
-Once you have you extension in a git repository your `bundle` will use only the
-commited files to create the archive, but if your repository is dirty `pgxn-utils`
+Once you have your extension in a git repository your `bundle` will use only the
+commited files to create the archive, but if your repository is dirty then `pgxn-utils`
 will hint you to commit or stash your changes, before bundle.
 
 You must be careful with new files not added to repository, because they will NOT