diff --git a/PP/Doc/INPUT_DOS.def b/PP/Doc/INPUT_DOS.def
index 996ff2ede..f5aa49f6c 100644
--- a/PP/Doc/INPUT_DOS.def
+++ b/PP/Doc/INPUT_DOS.def
@@ -79,7 +79,7 @@ input_description -distribution {Quantum Espresso} -package PWscf -program dos.x
 	}
 
 	var fildos -type CHARACTER {
-	    default { "prefix".dos }
+	    default { "@ref prefix.dos" }
 	    info {
 		output file containing DOS(E)
 	    }
diff --git a/PP/Doc/INPUT_IMPORTEXPORT_BINARY.def b/PP/Doc/INPUT_IMPORTEXPORT_BINARY.def
index 51997a364..e26d52e67 100644
--- a/PP/Doc/INPUT_IMPORTEXPORT_BINARY.def
+++ b/PP/Doc/INPUT_IMPORTEXPORT_BINARY.def
@@ -74,7 +74,7 @@ input_description -distribution {Quantum Espresso} -package PWscf -program impor
 	    text {	    
 	       The utility will also expect to find, and copy, the 
 	       outdir/data-file.xml and the *.UPF pseudopotential files in the
-	       prefix.save subdirectory, and will copy them from the outdir
+	       @ref prefix.save subdirectory, and will copy them from the outdir
 	       to the newoutdir. It will then convert the charge density and
 	       spin polarization files in the correct format. Other files,
 	       in particular wavefunctions and the band structure (files
diff --git a/PP/Doc/INPUT_PROJWFC.def b/PP/Doc/INPUT_PROJWFC.def
index 639521bb5..6ccc7cd9a 100644
--- a/PP/Doc/INPUT_PROJWFC.def
+++ b/PP/Doc/INPUT_PROJWFC.def
@@ -85,7 +85,7 @@ input_description -distribution {Quantum Espresso} -package PWscf -program projw
 
         var filpdos -type CHARACTER {
             info { prefix for output files containing PDOS(E) } 
-            default { (value of prefix variable) }
+            default { (value of @ref prefix variable) }
         }
         
         var filproj -type CHARACTER {
diff --git a/PP/Doc/INPUT_bgw2pw.def b/PP/Doc/INPUT_bgw2pw.def
index eacd6fd9b..38da068dd 100644
--- a/PP/Doc/INPUT_bgw2pw.def
+++ b/PP/Doc/INPUT_bgw2pw.def
@@ -9,14 +9,14 @@ input_description -distribution {Quantum Espresso} -package PWscf -program bgw2p
 	   on top of the valence bands and want to diagonalize them in pw.x.
 	   Look at the documentation for SAPO code in BerkeleyGW for more information.
 
-	bgw2pw.x reads common parameters from file prefix.save/data-file.xml and
-	writes files prefix.save/charge-density.dat (charge density in R-space),
-	prefix.save/gvectors.dat (G-vectors for charge density and potential),
-	prefix.save/K$n/eigenval.xml (eigenvalues and occupations for nth k-point),
-	prefix.save/K$n/evc.dat (wavefunctions in G-space for nth k-point), and
-	prefix.save/K$n/gkvectors.dat (G-vectors for nth k-point).
+	bgw2pw.x reads common parameters from file @ref prefix.save/data-file.xml and
+	writes files @ref prefix.save/charge-density.dat (charge density in R-space),
+	@ref prefix.save/gvectors.dat (G-vectors for charge density and potential),
+	@ref prefix.save/K$n/eigenval.xml (eigenvalues and occupations for nth k-point),
+	@ref prefix.save/K$n/evc.dat (wavefunctions in G-space for nth k-point), and
+	@ref prefix.save/K$n/gkvectors.dat (G-vectors for nth k-point).
 
-	bgw2pw.x doesn't modify file prefix.save/data-file.xml so make changes to this
+	bgw2pw.x doesn't modify file @ref prefix.save/data-file.xml so make changes to this
 	file manually (for example, you will need to change the number of bands if you
 	are using bgw2pw.x in conjunction with SAPO code in BerkeleyGW).
 
diff --git a/PP/Doc/INPUT_pw_export.def b/PP/Doc/INPUT_pw_export.def
index a1b9693ca..175d0e886 100644
--- a/PP/Doc/INPUT_pw_export.def
+++ b/PP/Doc/INPUT_pw_export.def
@@ -69,9 +69,9 @@ input_description -distribution {Quantum Espresso} -package PWscf -program pw_ex
 	    info {
 		Output file. 
 
-		If it is omitted, a directory "prefix.export/" is created 
+		If it is omitted, a directory "@ref prefix.export/" is created 
 		in outdir and some output files are put there. Anyway all the data
-		are accessible through the "prefix.export/index.xml" file which
+		are accessible through the "@ref prefix.export/index.xml" file which
 		contains implicit pointers to all the other files in the
 		export directory. If reading is done by the IOTK library
 		all data appear to be in index.xml even if physically it is not.