diff options
authorAvatar Mike Kelly <pioto@pioto.org> 2006-09-01 17:20:29 +0000
committerAvatar Mike Kelly <pioto@pioto.org> 2006-09-01 17:20:29 +0000
commit7ed33a4dacfb29784aaecd2e5d7d59892fcb9834 (patch)
parent29998781c14d6963df8d602d5201e4b298407792 (diff)
Use \ref foo instead of <a href="#foo"> to reference different sections. Fix a typo.
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/doc_migration_howto.doxygen b/doc/doc_migration_howto.doxygen
index 899a8e8..ee544ae 100644
--- a/doc/doc_migration_howto.doxygen
+++ b/doc/doc_migration_howto.doxygen
@@ -8,9 +8,9 @@
about Paludis. Read the \link KnownIssues known issues \endlink list.
There are two methods you can follow to migrate from Portage to Paludis, the
-<a href="#MigrationHowtoPortageToPaludisManual">Manual Method</a>, and the
-<a href="#MigrationHowtoPortageToPaludisAutomated">Automated Method</a>. Also,
-it is now usually possible to migrate <a href="#MigrationHowtoPaludisToPortage">from Paludis back to Portage</a>.
+\ref MigrationHowtoPortageToPaludisManual "Manual Method", and the \ref
+MigrationHowtoPortageToPaludisAutomated "Automated Method". Also, it is now
+usually possible to migrate \ref MigrationHowtoPaludisToPortage "from Paludis back to Portage".
\section MigrationHowtoPortageToPaludisAutomated How to Migrate from Portage to Paludis (the automated method)
@@ -72,7 +72,7 @@ or the script will bail out. This is to prevent it from clobbering an existing
paludis config. Also, the script will not migrate your customized portage
bashrc, that is somethign you will have to do on your own.
-The script will migrate your <code>PORTDIR_OVERLAYS</code> to Plaudis as best as
+The script will migrate your <code>PORTDIR_OVERLAYS</code> to Paludis as best as
possible, but, currently, Paludis doesn't support all the sync methods that
<i>layman</i> does, so you will still probably want to run <code>layman
-S</code> to update any layman repositories you have now. Finally, the script