aboutsummaryrefslogtreecommitdiffstats
path: root/README.md
diff options
context:
space:
mode:
authorSJ.Yoon <gg.sj.yoon@gmail.com>2014-09-04 08:48:29 -0400
committerSJ.Yoon <gg.sj.yoon@gmail.com>2014-09-04 08:48:29 -0400
commiteaa143629e73ea844d4180d6b1439a2a3293ef5c (patch)
treeb552b730a52588e6a1b00eb3ac658e5d6cd7d0c0 /README.md
parent3e1880f0fcf6dd0f2b52e6817c1a4b70669d46ce (diff)
downloadpf4j-eaa143629e73ea844d4180d6b1439a2a3293ef5c.tar.gz
pf4j-eaa143629e73ea844d4180d6b1439a2a3293ef5c.zip
Fixed typos in README.md
Diffstat (limited to 'README.md')
-rw-r--r--README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/README.md b/README.md
index 4438b86..b1a8835 100644
--- a/README.md
+++ b/README.md
@@ -171,7 +171,7 @@ Plugin assembly
After you developed a plugin the next step is to deploy it in your application. For this task, one option is to create a zip file with a structure described in section [How to use](https://github.com/decebals/pf4j/blob/master/README.md#how-to-use) from the beginning of the document.
If you use `apache maven` as build manger than your pom.xml file must looks like [this](https://github.com/decebals/pf4j/blob/master/demo/plugins/plugin1/pom.xml). This file it's very simple and it's self explanatory.
-If you use `apache ant` than your buil.xml file must looks like [this](https://github.com/gitblit/gitblit-powertools-plugin/blob/master/build.xml). In this case please look at the "build" target.
+If you use `apache ant` then your build.xml file must looks like [this](https://github.com/gitblit/gitblit-powertools-plugin/blob/master/build.xml). In this case please look at the "build" target.
Plugin lifecycle
--------------------------