summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorStephen Paulger <stephenpaulger@users.noreply.github.com>2015-09-16 12:05:28 +0100
committerTim Graham <timograham@gmail.com>2015-09-16 09:35:37 -0400
commit52c1212726a49f14cf4c70f72bbf9b87524c330d (patch)
treedb77ee9d00e26962cfac6197b0d4dbe3d2fe5121 /docs
parent688f8de7b612545e4dd25f4707bb18ccecc255ce (diff)
[1.8.x] Removed unnecessarily rude terminology.
Backport of 443dffbeb214da18a0a4204b5295c2b97df418ab from master
Diffstat (limited to 'docs')
-rw-r--r--docs/ref/contrib/sites.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/ref/contrib/sites.txt b/docs/ref/contrib/sites.txt
index 3270850f11..46a63ad4fb 100644
--- a/docs/ref/contrib/sites.txt
+++ b/docs/ref/contrib/sites.txt
@@ -53,7 +53,7 @@ Kansas. LJWorld.com focuses on news, while Lawrence.com focuses on local
entertainment. But sometimes editors want to publish an article on *both*
sites.
-The brain-dead way of solving the problem would be to require site producers to
+The naive way of solving the problem would be to require site producers to
publish the same story twice: once for LJWorld.com and again for Lawrence.com.
But that's inefficient for site producers, and it's redundant to store
multiple copies of the same story in the database.