From e731de57556dadd62b3148aaad5d83652a86eff7 Mon Sep 17 00:00:00 2001
From: Dale Wijnand <344610+dwijnand@users.noreply.github.com>
Date: Fri, 7 Sep 2018 11:46:53 +0100
Subject: [PATCH 1/2] No copyright notices on new tests

---
 src/tests/adding.md | 1 -
 1 file changed, 1 deletion(-)

diff --git a/src/tests/adding.md b/src/tests/adding.md
index ee264747a..dca224fff 100644
--- a/src/tests/adding.md
+++ b/src/tests/adding.md
@@ -9,7 +9,6 @@ To add a new test, the first thing you generally do is to create a
 file, typically a Rust source file. Test files have a particular
 structure:
 
-- They always begin with the [copyright notice](./conventions.html#copyright);
 - then they should have some kind of
   [comment explaining what the test is about](#explanatory_comment);
 - next, they can have one or more [header commands](#header_commands), which

From ad03ec4ee8e1f1579018f5ed879e06d881b2ea31 Mon Sep 17 00:00:00 2001
From: Dale Wijnand <344610+dwijnand@users.noreply.github.com>
Date: Fri, 7 Sep 2018 11:47:56 +0100
Subject: [PATCH 2/2] Write in English

---
 src/tests/adding.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/tests/adding.md b/src/tests/adding.md
index dca224fff..b9f05b9dd 100644
--- a/src/tests/adding.md
+++ b/src/tests/adding.md
@@ -9,7 +9,7 @@ To add a new test, the first thing you generally do is to create a
 file, typically a Rust source file. Test files have a particular
 structure:
 
-- then they should have some kind of
+- They should have some kind of
   [comment explaining what the test is about](#explanatory_comment);
 - next, they can have one or more [header commands](#header_commands), which
   are special comments that the test interpreter knows how to interpret.