Documentation.

diff --git a/docs/00_index.mkd b/docs/00_index.mkd
index df3ac850c651c924f60eacae321ba561bc210c69..80c1148de7740fec59d50dc181545252b175e8d9 100644 (file)
--- a/docs/00_index.mkd
+++ b/docs/00_index.mkd
@@ -32,6 +32,10 @@ It's designed primarily as a tool for small workgroups who want to host centrali
 \r
 You can browse a live demo [here](http://demo-gitblit.rhcloud.com) hosted on [RedHat's OpenShift][rhcloud] cloud service.\r
 \r
+**NOTE:**  \r
+The demo is a bit unstable due to a bug in JBossAS7/Tomcat when running in LOW_MEMORY mode which OpenShift mandates.  \r
+RedHat engineers hope to have this issue resolved soon.\r
+\r
 ### GO: Single-Stack Solution\r
 \r
 *Gitblit GO* is an integrated, single-stack solution based on Jetty.\r

diff --git a/docs/01_setup.mkd b/docs/01_setup.mkd
index f798e6d153f55ebd41c798c9f03cf6123ccc1897..8b5702b69ca1c0fa3410aeb4243065e4ee2e0130 100644 (file)
--- a/docs/01_setup.mkd
+++ b/docs/01_setup.mkd
@@ -242,7 +242,7 @@ Please see the following interface definition [com.gitblit.IUserService](https:/
 \r
 *SINCE 0.8.0*\r
 \r
-The preferred hook mechanism is Groovy.  This mechanism only executes when pushing to Gitblit, not when pushing to some other Git tooling in your stack.\r
+Gitblit uses Groovy for its push hook mechanism.  This mechanism only executes when pushing to Gitblit, not when pushing to some other Git tooling in your stack.\r
 \r
 The Groovy hook mechanism allows for dynamic extension of Gitblit to execute custom tasks on receiving and processing push events.  The scripts run within the context of your Gitblit instance and therefore have access to Gitblit's internals at runtime.\r
 \r

diff --git a/docs/04_releases.mkd b/docs/04_releases.mkd
index da0566208d6365f982d4d2127328a6967f4f9870..0ef4d3f2faea928c34793cb60e3281be06c5c5aa 100644 (file)
--- a/docs/04_releases.mkd
+++ b/docs/04_releases.mkd
@@ -12,7 +12,7 @@ Hook scripts can be set per-repository, per-team, or globally for all repositori
     **New:** *groovy.postReceiveScripts =*\r
 - *sendmail.groovy* for optional email notifications on push.  \r
 You must properly configure your SMTP server settings in `gitblit.properties` or `web.xml` to use *sendmail.groovy*.\r
-- New global key for mailing lists.  This is used in conjunction with the *sendmail.groovy* hook script.  All repositories that use the *sendmail.groovy* script will include these addresses in the notification process.  \r
+- New global key for mailing lists.  This is used in conjunction with the *sendmail.groovy* hook script.  All repositories that use the *sendmail.groovy* script will include these addresses in the notification process.  Please see the Setup page for more details about configuring sendmail.  \r
     **New:** *mail.mailingLists =*\r
 - *com.gitblit.GitblitUserService*.  This is a wrapper object for the built-in user service implementations.  For those wanting to only implement custom authentication it is recommended to subclass GitblitUserService and override the appropriate methods.  Going forward, this will help insulate custom authentication from new IUserService API and/or changes in model classes.\r
 - New default user service implementation: *com.gitblit.ConfigUserService* (`users.conf`)  \r
@@ -33,8 +33,7 @@ The original `users.properties` file and it's corresponding implementation are *
    **New:** *web.allowFlashCopyToClipboard = true*\r
 - JavaScript-based 3-step (click, ctrl+c, enter) *copy to clipboard* of the primary repository url in the event that you do not want to use Flash on your installation\r
 - Empty repositories now link to an *empty repository* page which gives some direction to the user for the next step in using Gitblit.  This page displays the primary push/clone url of the repository and gives sample syntax for the git command-line client. (issue 31)\r
-- automatic *gh-pages* branch serving (Jekyll is not supported)  \r
-Gitblit does not checkout your gh-pages branch to a temporary filesystem, all page and resource requests are live through the repository\r
+- Repositories with a *gh-pages* branch will now have a *pages* link which will serve the content of this branch.  All resource requests are against the repository, Gitblit does not checkout/export this branch to a temporary filesystem.  Jekyll templating is not supported.\r
 - Gitblit Express bundle to get started running Gitblit on RedHat's OpenShift cloud <span class="label warning">BETA</span>\r
 \r
 #### changes\r