summaryrefslogtreecommitdiffstats
path: root/documentation/testing.page
diff options
context:
space:
mode:
authorluke <luke@980ebf18-57e1-0310-9a29-db15c13687c0>2006-06-18 00:00:30 +0000
committerluke <luke@980ebf18-57e1-0310-9a29-db15c13687c0>2006-06-18 00:00:30 +0000
commit3772aaf3d3d96058d9a88b86e477e9845fc49736 (patch)
tree8af821609f1f256954f2786d955fbada5b6b2275 /documentation/testing.page
parente891ffb0280bb13411d4614d9ae4be3522d291cc (diff)
downloadpuppet-3772aaf3d3d96058d9a88b86e477e9845fc49736.tar.gz
puppet-3772aaf3d3d96058d9a88b86e477e9845fc49736.tar.xz
puppet-3772aaf3d3d96058d9a88b86e477e9845fc49736.zip
further work on converting from rst to markdown
git-svn-id: https://reductivelabs.com/svn/puppet/trunk@1296 980ebf18-57e1-0310-9a29-db15c13687c0
Diffstat (limited to 'documentation/testing.page')
-rw-r--r--documentation/testing.page8
1 files changed, 4 insertions, 4 deletions
diff --git a/documentation/testing.page b/documentation/testing.page
index c19c8697c..7ebe49e54 100644
--- a/documentation/testing.page
+++ b/documentation/testing.page
@@ -4,7 +4,7 @@ title: Testing
---
If you want to just test-drive Puppet, making the least commitment possible,
-you can run it directly from the checked-out source_, against a configuration
+you can run it directly from the checked-out [source][], against a configuration
in a temporary directory.
The default Puppet configuration directory (where it looks for its manifests,
@@ -55,7 +55,7 @@ and run it. In noop mode, this should work for any user, but if you run it as
a normal user you might get some errors if you are not in noop mode (e.g.,
normal users cannot use 'chown').
-Note that your ``site.pp`` file should have a node_ definition for the host
+Note that your ``site.pp`` file should have a [node][] definition for the host
connecting; otherwise you will get an error complaining of no configuration for
that host. It is possible to skip this requirement -- see the ``--help``
output of ``puppetmasterd`` for details.
@@ -83,5 +83,5 @@ element, all the way up to the base of the configuration, and it is also
tagged with the host name. So if 'classA' includes 'classB' which creates
'fileC', then 'fileC' will be tagged with both classes.
-.. _node: structures#nodes
-.. _source: fromsvn
+[node]: structures#nodes
+[source]: fromsvn