4 files changed, 18 insertions, 9 deletions
diff --git a/docs/00_index.mkd b/docs/00_index.mkd
index bee0635e..df3ac850 100644
--- a/docs/00_index.mkd
+++ b/docs/00_index.mkd
@@ -73,7 +73,7 @@ Administrators can create and manage all repositories, user accounts, and teams
 
 ### Backup Strategy
 
-Gitblit includes a backup mechanism (*federation*) which can be used to backup repositories and, optionally, user accounts & server settings from your Gitblit instance to another Gitblit instance or to a [Gitblit Federation Client](http://code.google.com/p/gitblit/downloads/detail?name=%FEDCLIENT%).  Similarly, you can use the federation mechanism to aggregate individual workspace Gitblit instances to a common, centralized server.
+Gitblit includes a backup mechanism (*federation*) which can be used to backup repositories and, optionally, user accounts, team definitions, server settings, & Groovy push hook scripts from your Gitblit instance to another Gitblit instance or to a [Gitblit Federation Client](http://code.google.com/p/gitblit/downloads/detail?name=%FEDCLIENT%).  Similarly, you can use the federation mechanism to aggregate individual workspace Gitblit instances to a common, centralized server.
 
 ### Java Runtime Requirement
 
diff --git a/docs/01_features.mkd b/docs/01_features.mkd
index 7d33911b..a5856a1c 100644
--- a/docs/01_features.mkd
+++ b/docs/01_features.mkd
@@ -17,6 +17,7 @@
 - Administrators may create, edit, rename, or delete users through the web UI or RPC interface
 - Administrators may create, edit, rename, or delete teams through the web UI or RPC interface
 - Repository Owners may edit repositories through the web UI
+- Gravatar integration
 - Git-notes display support
 - Branch metrics (uses Google Charts)
 - HEAD and Branch RSS feeds
diff --git a/docs/02_federation.mkd b/docs/02_federation.mkd
index 6525000e..0aaae4fa 100644
--- a/docs/02_federation.mkd
+++ b/docs/02_federation.mkd
@@ -13,7 +13,7 @@ Please review all the documentation to understand how it works and its limitatio
 
 ### Important Changes to Note
 
-The *Gitblit 0.8.0* federation protocol adds retrieval of team definitions.  Older clients will not know to request team information. 
+The *Gitblit 0.8.0* federation protocol adds retrieval of teams and referenced push scripts.  Older clients will not know to request team or push script information. 
 
 The *Gitblit 0.7.0* federation protocol is incompatible with the 0.6.0 federation protocol because of a change in the way timestamps are formatted.
 
@@ -54,7 +54,7 @@ String usersAndRepositoriesToken = SHA1(passphrase + "-USERS_AND_REPOSITORIES");
 String repositoriesToken = SHA1(passphrase + "-REPOSITORIES");
 %ENDCODE%
     
-The *ALL* token allows another Gitblit instance to pull all your repositories, user accounts, and server settings.  
+The *ALL* token allows another Gitblit instance to pull all your repositories, user accounts, server settings, and referenced push scripts.  
 The *USERS_AND_REPOSITORIES* token allows another Gitblit instance to pull all your repositories and  user accounts.  
 The *REPOSITORIES* token only allows pulling of the repositories.
 
@@ -173,9 +173,17 @@ The pulling Gitblit instance will store a registration-specific `gitblit.propert
 
 These settings are unused by the pulling Gitblit instance.
 
+#### Push Scripts 
+
+Your Groovy push scripts are only pulled when using the *ALL* token.
+
+The pulling Gitblit instance will retrieve any referenced (i.e. used) push script and store it locally as *registration_scriptName.groovy* in the *federation.N.folder* folder.
+
+These scripts are unused by the pulling Gitblit instance.
+
 ### Collisions and Conflict Resolution
 
-Gitblit does **not** detect conflict and it does **not** offer conflict resolution of repositories, users, or settings.
+Gitblit does **not** detect conflict and it does **not** offer conflict resolution of repositories, users, teams, or settings.
 
 If an object exists locally that has the same name as the remote object, it is assumed they are the same and the contents of the remote object are merged into the local object.  If you can not guarantee that this is the case, then you should not store any federated repositories directly in *git.repositoriesFolder* and you should not enable *mergeAccounts*.
 
@@ -250,9 +258,9 @@ These examples would be entered into the `gitblit.properties` file of the pullin
 
 This assumes that the *token* is the *ALL* token from the origin gitblit instance.
 
-The repositories, example1_users.conf, and example1_gitblit.properties will be put in *git.repositoriesFolder* and the origin user accounts will be merged into the local user accounts, including passwords and all roles.  The Gitblit instance will also send a status acknowledgment to the origin Gitblit instance at the end of the pull operation.  The status report will include the state of each repository pull (EXCLUDED, SKIPPED, NOCHANGE, PULLED, MIRRORED).  This way the origin Gitblit instance can monitor the health of its mirrors.
+The repositories, example1_users.conf, example1_gitblit.propertiesn and all example1_scripts.groovy will be put in *git.repositoriesFolder* and the origin user accounts will be merged into the local user accounts, including passwords and all roles.  The Gitblit instance will also send a status acknowledgment to the origin Gitblit instance at the end of the pull operation.  The status report will include the state of each repository pull (EXCLUDED, SKIPPED, NOCHANGE, PULLED, MIRRORED).  This way the origin Gitblit instance can monitor the health of its mirrors.
 
-This example is considered *nearly* perfect because while the origin Gitblit's server settings are pulled and saved locally, they are not merged with your server settings so its not a true mirror, but its likely the mirror you'd want to configure.
+This example is considered *nearly* perfect because while the origin Gitblit's server settings & push scripts are pulled and saved locally, they are not merged with your server settings so its not a true mirror.
 
     federation.example1.url = https://go.gitblit.com
     federation.example1.token = 6f3b8a24bf970f17289b234284c94f43eb42f0e4
diff --git a/docs/04_releases.mkd b/docs/04_releases.mkd
index db47d416..b87ebbb0 100644
--- a/docs/04_releases.mkd
+++ b/docs/04_releases.mkd
@@ -5,7 +5,7 @@
 
 - updated: Gitblit GO is now monolithic like the WAR build. (issue 30)  
 This change helps adoption of GO in environments without an internet connection or with a restricted connection.
-- added: Groovy 1.8.4 and a push hook script mechanism.  Hook scripts can be set per-repository, pre-team, or globally for all repositories.  
+- added: Groovy 1.8.4 and a push hook script mechanism.  Hook scripts can be set per-repository, per-team, or globally for all repositories.  
 Unfortunately this adds another 6 MB to the 8MB Gitblit package, but it allows for a *very* powerful, flexible, platform-independent hook script mechanism.  
     **New:** *groovy.scriptsFolder = groovy*  
     **New:** *groovy.preReceiveScripts =*  
@@ -18,11 +18,11 @@ Unfortunately this adds another 6 MB to the 8MB Gitblit package, but it allows f
 This user service implementation allows for serialization and deserialization of more sophisticated Gitblit User objects and will open the door for more advanced Gitblit features. For upgrading installations, a `users.conf` file will automatically be created for you from your existing `users.properties` file on your first launch of Gitblit.  You will have to manually set *realm.userService=users.conf* to switch to the new user service.  
 The original `users.properties` file and it's corresponding implementation are **deprecated**.  
     **New:** *realm.userService = users.conf*
-- added: Teams for specifying user-repository access in bulk
+- added: Teams for specifying user-repository access in bulk.  Teams may also specify mailing lists addresses and pre- & post- receive hook scripts.
 - added: Gitblit Express bundle to get started running Gitblit on RedHat's OpenShift cloud
 - added: optional Gravatar integration  
     **New:** *web.allowGravatar = true*   
-- added: multi-repository activity page.  this is a timeline of commit activity over the last N days for one or more repositories.  
+- added: aggregated repository activity page.  this is a timeline of commit activity over the last N days for one or more repositories.  
    **New:** *web.activityDuration = 14*  
    **New:** *web.timeFormat = HH:mm*  
    **New:** *web.datestampLongFormat = EEEE, MMMM d, yyyy*