From 43ab759ce3dffa796a95c1fe8679bc3c3eee2700 Mon Sep 17 00:00:00 2001 From: Baptiste Mispelon Date: Wed, 25 Sep 2013 18:20:33 +0200 Subject: [PATCH] [1.5.X] Fixed wording in unit tests documentation. Backport of 42b9feb2e79546e1d4362c3a4f0043f3c569ace3 from master. --- docs/internals/contributing/writing-code/unit-tests.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/internals/contributing/writing-code/unit-tests.txt b/docs/internals/contributing/writing-code/unit-tests.txt index 1770e4aa63..07d7de982e 100644 --- a/docs/internals/contributing/writing-code/unit-tests.txt +++ b/docs/internals/contributing/writing-code/unit-tests.txt @@ -65,8 +65,8 @@ two databases: If you're using a backend that isn't SQLite, you will need to provide other details for each database: -* The :setting:`USER` option for each of your databases needs to - specify an existing user account for the database. +* The :setting:`USER` option needs to specify an existing user account + for the database. * The :setting:`PASSWORD` option needs to provide the password for the :setting:`USER` that has been specified.