summaryrefslogtreecommitdiff
path: root/docs/howto/initial-data.txt
diff options
context:
space:
mode:
Diffstat (limited to 'docs/howto/initial-data.txt')
-rw-r--r--docs/howto/initial-data.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/howto/initial-data.txt b/docs/howto/initial-data.txt
index aafe14cc76..7a43196957 100644
--- a/docs/howto/initial-data.txt
+++ b/docs/howto/initial-data.txt
@@ -2,7 +2,7 @@
How to provide initial data for models
======================================
-It's sometimes useful to pre-populate your database with hard-coded data when
+It's sometimes useful to prepopulate your database with hard-coded data when
you're first setting up an app. You can provide initial data with migrations or
fixtures.
@@ -76,7 +76,7 @@ You'll store this data in a ``fixtures`` directory inside your app.
You can load data by calling :djadmin:`manage.py loaddata <loaddata>`
``<fixturename>``, where ``<fixturename>`` is the name of the fixture file
you've created. Each time you run :djadmin:`loaddata`, the data will be read
-from the fixture and re-loaded into the database. Note this means that if you
+from the fixture and reloaded into the database. Note this means that if you
change one of the rows created by a fixture and then run :djadmin:`loaddata`
again, you'll wipe out any changes you've made.