diff --git a/classes/class_torrent.php b/classes/class_torrent.php
index 93e90409..f6863a94 100644
--- a/classes/class_torrent.php
+++ b/classes/class_torrent.php
@@ -262,7 +262,7 @@ function file_list() {
 				$TotalSize+=$File->Val['length'];
 				$FileSize = $File->Val['length'];
 				
-				$FileName = implode('/',$File->Val['path']->Val);
+				$FileName = ltrim(implode('/',$File->Val['path']->Val), '/');
 				
 				$FileList[] = array($FileSize, $FileName);
 				$FileNames[] = $FileName;
diff --git a/sections/rules/upload.php b/sections/rules/upload.php
index 4f2f6dfe..f76bfb63 100644
--- a/sections/rules/upload.php
+++ b/sections/rules/upload.php
@@ -396,7 +396,7 @@
 						<li id="r2.2.15.8"><a href="#r2.2.15"><strong>&uarr;_</strong></a> <a href="#r2.2.15.8">2.2.15.8.</a> <strong>FLAC rips that contain ID3 tags or other non-compliant tags for FLAC may be trumped by same score rips that have faulty tags removed and replaced with the standard for each format.</strong> Enabling ID3 tags in <a href="http://www.exactaudiocopy.de/">EAC</a> when ripping to FLAC may prevent some players from playing the files due to the inclusion of ID3 headers. If you wish to trump a FLAC rip that was ripped with ID3 tags enabled, upload the corrected torrent with the proper Vorbis comments, and report the old torrent. Add information about your clean-up in the <em>Release description</em>, or your torrent may be deleted for a dupe. Do not edit the log and change the ID3 tag setting to "No." <em>Note: A simple way of getting rid of the ID3 header is to decompress the files to WAV. Then compress the files to FLAC, and again add the proper Vorbis comments.</em>
 
 						</li>
-						<li id="r2.2.15.9"><a href="#r2.2.15"><strong>&uarr;_</strong></a> <a href="#r2.2.15.9">2.2.15.9.</a> <strong>No log editing is permitted.</strong> You may change the path of the files to hide your username or personal info in the home directory (e.g. C:\Documents and Settings\MyRealName\My Documents\) after ripping if need be. No other log editing is permitted. Forging log data is a serious misrepresentation of quality, and will result in a warning and permanent loss of upload privileges if found. <strong>Do not consolidate logs under any circumstances.</strong> If you must re-rip a disc and happen to have the new log appended to the original, leave them as-is. Do not remove any part of either log, and never copy/paste parts of a new log over an old log. If you find that an appended log has not been scored properly, please PM a moderator to get the score manually adjusted.
+						<li id="r2.2.15.9"><a href="#r2.2.15"><strong>&uarr;_</strong></a> <a href="#r2.2.15.9">2.2.15.9.</a> <strong>No log editing is permitted.</strong> Forging log data is a serious misrepresentation of quality, and will result in a warning and permanent loss of upload privileges if found. <strong>Do not consolidate logs under any circumstances.</strong> If you must re-rip a disc and happen to have the new log appended to the original, leave them as-is. Do not remove any part of either log, and never copy/paste parts of a new log over an old log. If you find that an appended log has not been scored properly, please PM a moderator to get the score manually adjusted.
 						</li>
 
 					</ul>