From b32b111dbd43d9ea9ef53a633d71256b1562b1de Mon Sep 17 00:00:00 2001
From: Mike Little <mikelittle@git.wordpress.org>
Date: Wed, 8 Oct 2003 22:33:27 +0000
Subject: [PATCH] Wrapped text

git-svn-id: https://develop.svn.wordpress.org/trunk@439 602fd350-edb4-49c9-b593-d223f7449a82
---
 wp-admin/upgrade-071-to-072.php | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/wp-admin/upgrade-071-to-072.php b/wp-admin/upgrade-071-to-072.php
index d7fc552dc3..8e89409efa 100644
--- a/wp-admin/upgrade-071-to-072.php
+++ b/wp-admin/upgrade-071-to-072.php
@@ -61,7 +61,13 @@ switch($step) {
   configure in this file is your database connection info, and your table names.
   All other configuration info is now held in the database.</li>
 
-  <li>It is a fairly common error to have the table names wrong in wp-config.php if you&#8217;re coming from a legacy b2 installation. In a clean WordPress installation the tables are named things like <code>wp_posts</code> and <code>wp_comments</code>, but if you&#8217;re coming from b2 you probably have table names like <code>b2posts</code> and <code>b2comments</code>. Double-check the <code>$table_prefix</code> variable to make sure this has what is appropiate to your installation.</li>
+  <li>It is a fairly common error to have the table names wrong in wp-config.php
+  if you&#8217;re coming from a legacy b2 installation. In a clean WordPress
+  installation the tables are named things like <code>wp_posts</code> and
+  <code>wp_comments</code>, but if you&#8217;re coming from b2 you probably have
+  table names like <code>b2posts</code> and <code>b2comments</code>.
+  Double-check the <code>$table_prefix</code> variable to make sure this has
+  what is appropiate to your installation.</li>
 
   <li>If you have any troubles check out the <a
   href="http://wordpress.org/support/">support forums</a>.</li>