[sling-site] branch master updated: Fixed table display on configuration page

[je...@apache.org]

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

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


The following commit(s) were added to refs/heads/master by this push:
     new aac43c5  Fixed table display on configuration page
aac43c5 is described below

commit aac43c54cba7f3edf87dd61d60ffc449c6dc1c06
Author: JE Bailey <ja...@sas.com>
AuthorDate: Fri Jul 26 08:44:24 2019 -0400

    Fixed table display on configuration page
---
 src/main/jbake/content/documentation/configuration.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/main/jbake/content/documentation/configuration.md b/src/main/jbake/content/documentation/configuration.md
index 87884f6..c193e87 100644
--- a/src/main/jbake/content/documentation/configuration.md
+++ b/src/main/jbake/content/documentation/configuration.md
@@ -63,9 +63,9 @@ In addition the following command line arguments are accepted:
 | `-l loglevel` | `org.apache.sling.osgi.log.level` | The initial loglevel (0..4, FATAL, ERROR, WARN, INFO, DEBUG) |
 | `-f logfile` | `org.apache.sling.osgi.log.file` | The log file, "-" for stdout |
 | `-c slinghome` | `sling.home` | the sling context directory |
-| `-a address` | -- | the interfact to bind to (use 0.0.0.0 for any) (not supported yet) |
+| `-a address` |  | the interfact to bind to (use 0.0.0.0 for any) (not supported yet) |
 | `-p port` | `org.osgi.service.http.port` | the port to listen to (default 8080) |
-| `-h` | -- | Prints a simple usage message and exits. |
+| `-h` |  | Prints a simple usage message and exits. |
 
 The standalone application exits with status code 0 (zero) if Sling terminates normally, that is if the OSGi framework is stopped or if just the usage note has been displayed. If any error occurrs during command line parsing, the cause is printed to the error output and the application exists with status code 1 (one). If the OSGi framework fails to start, the cause is printed to the error output and the application exists with status code 2.