[2.2.x] Fixed #30184 -- Removed ellipsis characters from shell output strings.

Partially reverted 50b8493581fea3d7137dd8db33bac7008868d23a (refs #29654)
to avoid a crash when the user shell doesn't support non-ASCII characters.
Backport of 2bd8df243ac6fc35e58c9fe90b20c9e42519a5ac from master.

5 files changed, 10 insertions, 10 deletions

diff --git a/docs/intro/tutorial01.txt b/docs/intro/tutorial01.txt
index 208a4f3a3b..56de527fac 100644
--- a/docs/intro/tutorial01.txt
+++ b/docs/intro/tutorial01.txt
@@ -131,7 +131,7 @@ You'll see the following output on the command line:
 
 .. parsed-literal::
 
-    Performing system checks…
+    Performing system checks...
 
     System check identified no issues (0 silenced).
 
diff --git a/docs/intro/tutorial02.txt b/docs/intro/tutorial02.txt
index 4d2a62bec2..9046d167b0 100644
--- a/docs/intro/tutorial02.txt
+++ b/docs/intro/tutorial02.txt
@@ -338,8 +338,8 @@ Now, run :djadmin:`migrate` again to create those model tables in your database:
     Operations to perform:
       Apply all migrations: admin, auth, contenttypes, polls, sessions
     Running migrations:
-      Rendering model states… DONE
-      Applying polls.0001_initial… OK
+      Rendering model states... DONE
+      Applying polls.0001_initial... OK
 
 The :djadmin:`migrate` command takes all the migrations that haven't been
 applied (Django tracks which ones are applied using a special table in your
diff --git a/docs/intro/tutorial05.txt b/docs/intro/tutorial05.txt
index 222bbf4972..42891a6ecd 100644
--- a/docs/intro/tutorial05.txt
+++ b/docs/intro/tutorial05.txt
@@ -203,7 +203,7 @@ In the terminal, we can run our test:
 
 and you'll see something like::
 
-    Creating test database for alias 'default'…
+    Creating test database for alias 'default'...
     System check identified no issues (0 silenced).
     F
     ======================================================================
@@ -218,7 +218,7 @@ and you'll see something like::
     Ran 1 test in 0.001s
 
     FAILED (failures=1)
-    Destroying test database for alias 'default'…
+    Destroying test database for alias 'default'...
 
 What happened is this:
 
@@ -257,14 +257,14 @@ past:
 
 and run the test again::
 
-    Creating test database for alias 'default'…
+    Creating test database for alias 'default'...
     System check identified no issues (0 silenced).
     .
     ----------------------------------------------------------------------
     Ran 1 test in 0.001s
 
     OK
-    Destroying test database for alias 'default'…
+    Destroying test database for alias 'default'...
 
 After identifying a bug, we wrote a test that exposes it and corrected the bug
 in the code so our test passes.
diff --git a/docs/topics/migrations.txt b/docs/topics/migrations.txt
index 4df05bdd67..f518341310 100644
--- a/docs/topics/migrations.txt
+++ b/docs/topics/migrations.txt
@@ -135,8 +135,8 @@ database to make sure they work as expected::
     Operations to perform:
       Apply all migrations: books
     Running migrations:
-      Rendering model states… DONE
-      Applying books.0003_auto… OK
+      Rendering model states... DONE
+      Applying books.0003_auto... OK
 
 Once the migration is applied, commit the migration and the models change
 to your version control system as a single commit - that way, when other
diff --git a/docs/topics/testing/overview.txt b/docs/topics/testing/overview.txt
index a0aab28d15..12efb381c7 100644
--- a/docs/topics/testing/overview.txt
+++ b/docs/topics/testing/overview.txt
@@ -279,7 +279,7 @@ When you run your tests, you'll see a number of messages as the test runner
 prepares itself. You can control the level of detail of these messages with the
 ``verbosity`` option on the command line::
 
-    Creating test database…
+    Creating test database...
     Creating table myapp_animal
     Creating table myapp_mineral