This is an automated email from the ASF dual-hosted git repository.

git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/incubator-plc4x-website.git


The following commit(s) were added to refs/heads/asf-site by this push:
     new 846a473  Site checkin for project PLC4X: Jenkins Tools
846a473 is described below

commit 846a4739cdc0f3d18070a4c1da235b19aa3291e7
Author: jenkins <[email protected]>
AuthorDate: Thu Mar 21 08:56:10 2019 +0000

    Site checkin for project PLC4X: Jenkins Tools
---
 developers/building.html     |  2 +-
 developers/contributing.html | 10 +++++-----
 2 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/developers/building.html b/developers/building.html
index 8ed3fab..102af23 100644
--- a/developers/building.html
+++ b/developers/building.html
@@ -227,7 +227,7 @@
   <div class="sect2"> 
    <h3 id="_toc_using_the_maven-wrapper">Using the Maven-Wrapper</h3> 
    <div class="paragraph"> 
-    <p>The so-called <code>Maven-Wrapper</code> is used by calling the 
Maven-Wrapper scripts <code>mvnw</code> (Mac &amp; Linux) or 
<code>mvnw.cmd</code> (Windows) instead of the default Maven commads 
<code>mvn</code> and <code>mvn.cmd</code>.</p> 
+    <p>The so-called <code>Maven-Wrapper</code> is used by calling the 
Maven-Wrapper scripts <code>mvnw</code> (Mac &amp; Linux) or 
<code>mvnw.cmd</code> (Windows) instead of the default Maven commands 
<code>mvn</code> and <code>mvn.cmd</code>.</p> 
    </div> 
    <div class="paragraph"> 
     <p>These helpers ensure Maven is available in at least the version defined 
in <code>.mvn/maven-wrapper.properties</code>. If no suitable version can be 
found, it is automatically downloaded and installed alongside the project (So 
it doesn’t have to be downloaded every time and every project can have it’s own 
Maven version)</p> 
diff --git a/developers/contributing.html b/developers/contributing.html
index 05acbbd..e2b18d1 100644
--- a/developers/contributing.html
+++ b/developers/contributing.html
@@ -293,7 +293,7 @@
      </div> 
     </div> 
     <div class="paragraph"> 
-     <p>If you list all your remotes, wirth the following command:</p> 
+     <p>If you list all your remotes, with the following command:</p> 
     </div> 
     <div class="literalblock"> 
      <div class="content"> 
@@ -315,7 +315,7 @@ upstream    https://github.com/apache/incubator-plc4x.git 
(push)</pre>
      <p>If that’s so, you’re fine to continue, if not …​ well you could ask 
for assistance on our dev-list.</p> 
     </div> 
     <div class="paragraph"> 
-     <p>In order to get all changes of our upstream-repository, just execute 
the following commmand:</p> 
+     <p>In order to get all changes of our upstream-repository, just execute 
the following command:</p> 
     </div> 
     <div class="literalblock"> 
      <div class="content"> 
@@ -323,7 +323,7 @@ upstream    https://github.com/apache/incubator-plc4x.git 
(push)</pre>
      </div> 
     </div> 
     <div class="paragraph"> 
-     <p>This will get all changed from upstream and merge them locally. In 
order to update your GitHub version, you have to push things back to 
<code>origin</code>. You can do this by execunting the follwing command:</p> 
+     <p>This will get all changed from upstream and merge them locally. In 
order to update your GitHub version, you have to push things back to 
<code>origin</code>. You can do this by executing the following command:</p> 
     </div> 
     <div class="literalblock"> 
      <div class="content"> 
@@ -350,7 +350,7 @@ upstream    https://github.com/apache/incubator-plc4x.git 
(push)</pre>
     <p>Currently Apache has a separate login system for JIRA and all other 
services, this might change in the future, but right now it’s the way things 
are.</p> 
    </div> 
    <div class="paragraph"> 
-    <p>So if you are considering to contribute more than just a 
one-time-patch, please choose a username that hasn’t been used by an existing 
<a href="http://people.apache.org/committer-index.html";>Apache comitter</a> as 
this will simplify things if we invite you to become part of the team.</p> 
+    <p>So if you are considering to contribute more than just a 
one-time-patch, please choose a username that hasn’t been used by an existing 
<a href="http://people.apache.org/committer-index.html";>Apache committer</a> as 
this will simplify things if we invite you to become part of the team.</p> 
    </div> 
    <div class="paragraph"> 
     <p>If you want to be assigned to an issue because you want to work on it, 
please request to be added to the JIRA groups on our <a 
href="http://plc4x.apache.org/mailing-lists.html";>developers mailing 
list</a></p> 
@@ -362,7 +362,7 @@ upstream    https://github.com/apache/incubator-plc4x.git 
(push)</pre>
     <p>As our documentation and website are generated as a side-product of our 
build, contributing to this technically the same as contributing to the 
code.</p> 
    </div> 
    <div class="paragraph"> 
-    <p>All our content is written in Asciidoctor and is located in 
<code>src/site/asciidoc</code> directories. For a reference of the Asciidoctor 
snytax please have a look at the <a 
href="https://asciidoctor.org/docs/user-manual/#introduction-to-asciidoctor";>Asciidoctor
 documentation</a>.</p> 
+    <p>All our content is written in Asciidoctor and is located in 
<code>src/site/asciidoc</code> directories. For a reference of the Asciidoctor 
syntax please have a look at the <a 
href="https://asciidoctor.org/docs/user-manual/#introduction-to-asciidoctor";>Asciidoctor
 documentation</a>.</p> 
    </div> 
   </div> 
   <div class="sect2"> 

Reply via email to