diff --git a/PUprofile/README.md b/PUprofile/README.md
index 9aaa8f0cefd7efdbcf53cd0f2b11f44f791968e4..0df88577b4f3df56402fcdfa0f0df60fd4a43d17 100644
--- a/PUprofile/README.md
+++ b/PUprofile/README.md
@@ -1,7 +1,7 @@
 # PU profile tables
 
 Before blindly using the files provided here, one should check the current recommendations [TWiki](https://twiki.cern.ch/twiki/bin/viewauth/CMS/PileupJSONFileforData).  
-The `Run201?UL*.json` files provided here correspond to the UL recommendations for Run 2 analysis (2016, 2017, 2018) and are copies of the files found under `/afs/cern.ch/cms/CAF/CMSCOMM/COMM_DQM/certification/Collisions1?/13TeV/PileUp/UltraLegacy/pileup_latest*.txt`.  
+The `Run201*.json` files provided here correspond to the UL recommendations for Run 2 analysis (2016, 2017, 2018) and are copies of the files found under `/afs/cern.ch/cms/CAF/CMSCOMM/COMM_DQM/certification/Collisions1?/13TeV/PileUp/UltraLegacy/pileup_latest*.txt`.  
 These files can be used ontop data n-tuples to store the pile-up information per event (in principle per lumi section, in practice per event) via:  
  - the stand alone `applyPUlatest` executable  
  - the `mergeNtuples` executable, which contains the `applyPUlatest` correction
diff --git a/PUprofile/Run2016UL_postVFP.json b/PUprofile/Run2016_postVFP.json
similarity index 100%
rename from PUprofile/Run2016UL_postVFP.json
rename to PUprofile/Run2016_postVFP.json
diff --git a/PUprofile/Run2016UL_preVFP.json b/PUprofile/Run2016_preVFP.json
similarity index 100%
rename from PUprofile/Run2016UL_preVFP.json
rename to PUprofile/Run2016_preVFP.json
diff --git a/PUprofile/Run2017UL.json b/PUprofile/Run2017.json
similarity index 100%
rename from PUprofile/Run2017UL.json
rename to PUprofile/Run2017.json
diff --git a/PUprofile/Run2018UL.json b/PUprofile/Run2018.json
similarity index 100%
rename from PUprofile/Run2018UL.json
rename to PUprofile/Run2018.json