bold instead of italic looks better in fluido IMHO

git-svn-id: https://svn.apache.org/repos/asf/archiva/trunk@1391262 13f79535-47bb-0310-9956-ffa450edef68

2 files changed, 39 insertions, 38 deletions

diff --git a/archiva-docs/src/site/apt/adminguide/consumers.apt b/archiva-docs/src/site/apt/adminguide/consumers.apt
index b53149475..bf668fec2 100644
--- a/archiva-docs/src/site/apt/adminguide/consumers.apt
+++ b/archiva-docs/src/site/apt/adminguide/consumers.apt
@@ -38,23 +38,23 @@ Understanding Consumers in Apache Archiva
   each consumer processes them. There are 8 available repository content consumers which can be configured in the Repository Scanning
   page. These are:
   
-  * <auto-remove> - Removes files in the repository being scanned if the file type matches any of the configured file types to be removed.  
+  * <<auto-remove>> - Removes files in the repository being scanned if the file type matches any of the configured file types to be removed.  
   
-  * <auto-rename> - Automatically renames common artifact mistakes. 
+  * <<auto-rename>> - Automatically renames common artifact mistakes. 
   
-  * <create-missing-checksums> - Creates the md5 and sha1 checksum files of the artifact if there are none available in the repository.  
+  * <<create-missing-checksums>> - Creates the md5 and sha1 checksum files of the artifact if there are none available in the repository.  
   
-  * <index-content> - Adds the content of the artifact (specifically the pom) to the index, allowing the artifact to be searched in Archiva.
+  * <<index-content>> - Adds the content of the artifact (specifically the pom) to the index, allowing the artifact to be searched in Archiva.
   
-  * <metadata-updater> - Updates artifact metadata files depending on the content of the repository.  
+  * <<metadata-updater>> - Updates artifact metadata files depending on the content of the repository.  
   
-  * <repository-purge> - Removes old snapshots from the repository either by the number of days old or by the retention count.
+  * <<repository-purge>> - Removes old snapshots from the repository either by the number of days old or by the retention count.
 
-  * <validate-checksums> - Validates the checksum files of the artifact.
+  * <<validate-checksums>> - Validates the checksum files of the artifact.
 
-  * <create-archiva-metadata> - Take an artifact off of disk and put it into the metadata repository.
+  * <<create-archiva-metadata>> - Take an artifact off of disk and put it into the metadata repository.
 
-  * <duplicate-artifacts> - Search the artifact repository of known SHA1 Checksums for potential duplicate artifacts.
+  * <<duplicate-artifacts>> - Search the artifact repository of known SHA1 Checksums for potential duplicate artifacts.
 
   []
 
diff --git a/archiva-docs/src/site/apt/adminguide/repositories.apt b/archiva-docs/src/site/apt/adminguide/repositories.apt
index 33426601f..ae54fff8d 100644
--- a/archiva-docs/src/site/apt/adminguide/repositories.apt
+++ b/archiva-docs/src/site/apt/adminguide/repositories.apt
@@ -42,53 +42,54 @@ Understanding Repository Configuration of Apache Archiva
 
   Managed repository fields:
 
-  * <identifier> - the id of the repository. This must be unique.
+  * <<identifier>> - the id of the repository. This must be unique.
 
-  * <name> - the name of the repository.
+  * <<name>> - the name of the repository.
 
-  * <directory> - the location of the repository. If the path specified does not
+  * <<directory>> - the location of the repository. If the path specified does not
     exist, Archiva will create the missing directories.
 
-  * <index directory> - the location of the index files generated by Archiva. If
+  * <<index directory>> - the location of the index files generated by Archiva. If
     no location is specified, then the index directory (named <<<.indexer>>>)
     will be created at the root of the repository directory. Another directory
     named <<<.index>>> is also created at the root of the repository directory.
     This is not configurable though as it contains the packaged/bundled index
     which is consumed by different consumers of the index such as M2Eclipse.
 
-  * <type> - the repository layout (maven 2 or maven 1)
+  * <<type>> - the repository layout (maven 2 or maven 1)
 
-  * <cron> - the
-    {{{http://quartz.sourceforge.net/javadoc/org/quartz/CronTrigger.html}cron
-    schedule}} when repository scanning will be executed.
+  * <<cron>> - the
+    {{{http://quartz-scheduler.org/api/2.1.5/org/quartz/CronTrigger.html}cron schedule}} when 
+    repository scanning will be executed.
 
-  * <repository purge by days older> - the first option for repository purge.
+  * <<repository purge by days older>> - the first option for repository purge.
     Archiva will check how old the artifact is and if it is older than the set
     number of days in this field, then the artifact will be deleted respecting
-    the retention count (see #7) of course. In order to disable the purge by
+    the retention count of course. In order to disable the purge by
     number of days old and set Archiva to purge by retention count, just set the
     repository purge field to 0. The maximum number of days which can be set
     here is 1000. See the Repository Purge section below for more details.
+~~  above was:the retention count (see #7) of course no idea what is was linkeed to
 
-  * <repository purge by retention count> - the second option for repository
+  * <<repository purge by retention count>> - the second option for repository
     purge. When running the repository purge, Archiva will retain only the
     number of artifacts set for this field for a specific snapshot version. See
     the Repository Purge section below for more details.
 
-  * <releases included> - specifies whether there are released artifacts in the
+  * <<releases included>> - specifies whether there are released artifacts in the
     repository.
 
-  * <block re-deployment of released artifacts> - specifies whether released
+  * <<block re-deployment of released artifacts>> - specifies whether released
     artifacts that are already existing in the repository can be overwritten.
     Note that this only take effects for non-snapshot deployments.
 
-  * <snapshots included> - specifies whether there are snapshot artifacts in the
+  * <<snapshots included>> - specifies whether there are snapshot artifacts in the
     repository.
 
-  * <scannable> - specifies whether the repository can be scanned, meaning it is
+  * <<scannable>> - specifies whether the repository can be scanned, meaning it is
     a local repository which can be indexed, browsed, purged, etc.
 
-  * <delete released snapshots> - specifies whether to remove those snapshot
+  * <<delete released snapshots>> - specifies whether to remove those snapshot
     artifacts which already has release versions of it in the repository during
     repository purge.
 
@@ -116,39 +117,39 @@ http://[URL TO ARCHIVA]/repository/[REPOSITORY ID] (e.g. http://localhost:8080/a
 
   Remote repository fields:
 
-  * <identifier> - the id of the remote repository.
+  * <<identifier>> - the id of the remote repository.
 
-  * <name> - the name of the remote repository.
+  * <<name>> - the name of the remote repository.
 
-  * <url> - the url of the remote repository. It is also possible to use a
+  * <<url>> - the url of the remote repository. It is also possible to use a
     'file://' url to proxy a local repository. Be careful that if this local
     repository is a managed repository of archiva which has some proxies
     connectors, those ones won't be triggered.
 
-  * <username> - the username (if authentication is needed) to be used to access
+  * <<username>> - the username (if authentication is needed) to be used to access
     the repository.
 
-  * <password> - the password (if authentication is needed) to be used to access
+  * <<password>> - the password (if authentication is needed) to be used to access
     the repository.
 
-  * <type> - the layout (maven 2 or maven 1) of the remote repository.
+  * <<type>> - the layout (maven 2 or maven 1) of the remote repository.
 
-  * <Activate download remote index> - to activate downloading remote index to
+  * <<Activate download remote index>> - to activate downloading remote index to
     add available remote artifacts in search queries.
 
-  * <Remote index url, can be relative to url> - path of the remote index
+  * <<Remote index url, can be relative to url>> - path of the remote index
     directory.
 
-  * <Cron expression> - cron expression for downloading remote index (default
+  * <<Cron expression>> - cron expression for downloading remote index (default
     weekly on sunday)
 
-  * <Directory index storage> - path to store index directory, default will be
-    ${appserver.base}/data/remotes/${repositoryId}/.index
+  * <<Directory index storage>> - path to store index directory, default will be
+    $\{appserver.base\}/data/remotes/$\{repositoryId\}/.index
 
-  * <Download Remote Index Timeout in seconds> - read time out for downloading
+  * <<Download Remote Index Timeout in seconds>> - read time out for downloading
     remote index files (default 300)
 
-  * <Network Proxy to Use for download Remote Index> - proxy to use for
+  * <<Network Proxy to Use for download Remote Index>> - proxy to use for
     downloading remote index files.
 
 [../images/remote-repositories.png] Remote Repositories