summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorClaude Paroz <claude@2xlibre.net>2018-08-22 15:13:58 +0200
committerTim Graham <timograham@gmail.com>2018-08-22 09:13:58 -0400
commit50b8493581fea3d7137dd8db33bac7008868d23a (patch)
tree17e10260f66489ec5ecc60464e9fb94889c61aa2 /docs
parent233c70f0479beb3bff9027e6cff680882978fd4d (diff)
Refs #29654 -- Replaced three dots with ellipsis character in output strings.
Diffstat (limited to 'docs')
-rw-r--r--docs/intro/tutorial01.txt2
-rw-r--r--docs/intro/tutorial02.txt4
-rw-r--r--docs/intro/tutorial05.txt8
-rw-r--r--docs/topics/migrations.txt4
-rw-r--r--docs/topics/testing/overview.txt2
5 files changed, 10 insertions, 10 deletions
diff --git a/docs/intro/tutorial01.txt b/docs/intro/tutorial01.txt
index aca496580e..d387e2d6a7 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 c1f0aeef46..ea9c3dff56 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 c6c5e2900d..ad5d09ca1d 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 4fc1fdd47e..1073ce0cbe 100644
--- a/docs/topics/migrations.txt
+++ b/docs/topics/migrations.txt
@@ -134,8 +134,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 12efb381c7..a0aab28d15 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