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

rgielen pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/struts-site.git

commit 9e5caffa4b3e8e5768c594588cb6cd14a05c2c44
Author: Lukasz Lenart <lukaszlen...@apache.org>
AuthorDate: Sat Apr 11 19:05:42 2020 +0200

    Fixes md formatting
---
 source/updating-website.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/source/updating-website.md b/source/updating-website.md
index 620714f..d782c79 100644
--- a/source/updating-website.md
+++ b/source/updating-website.md
@@ -20,12 +20,12 @@ also any Pull Request should be opened against this branch 
as well.
 We are using Jekyll and mix of Markdown pages with raw Html pages, where 
Markdown is a preferred option.
 
 > WARN: do not manually change the `asf-site` or `ast-staging` branches, they 
 > will be automatically updated
-> by CI server. 
+> by a CI server. 
 
 The whole build of the website is orchestrated by 
[.asf.yaml](http://s.apache.org/asfyaml), please refer to the docs
 for more details. The main build of the website is performed by [a buildbot 
job](https://ci2.apache.org/#/builders/7),
-the staging site is build and deployed by [a Jenkins 
job](https://builds.apache.org/view/S-Z/view/Struts/job/Struts-staged-site/)
-- buildbot doesn't support staging site deployment yet.  
+the staging site is build and deployed by 
+[a Jenkins 
job](https://builds.apache.org/view/S-Z/view/Struts/job/Struts-staged-site/) - 
buildbot doesn't support staging site deployment yet.  
 
 ## Applying a change
 

Reply via email to