From 0b0fbdb04b2706c9a6fd83abe2b2ab2d38ba4c78 Mon Sep 17 00:00:00 2001
From: Philip Chimento <philip.chimento@gmail.com>
Date: Fri, 11 Feb 2022 16:58:28 -0800
Subject: [PATCH] Fix path example in generated test instructions

We should not have an absolute path (starting with a slash) in this
field, because that will mess up the test generation program.
---
 CONTRIBUTING.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 1e7686347a..c487b593a6 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -394,7 +394,7 @@ The Body of a test template matches that of a non-generated test in which an arb
 Expected [Frontmatter](#frontmatter) keys:
 Key | Description
 ------|-------------
-`path` | location within the published test hierarchy to output files created from this template, each with a path formed by appending the name of the corresponding test case file. For example, a template with `path` "/test/language/template1-" used by test case file case1.js will generate a test file for that case at "/test/language/template1-case1.js".
+`path` | location within the published test hierarchy to output files created from this template, each with a path formed by appending the name of the corresponding test case file. For example, a template with `path` "language/template1-" used by test case file case1.js will generate a test file for that case at "language/template1-case1.js".
 `name` | human-readable name of the syntactic form described by this template. Each generated test will have a `description` that is the result of appending the test template `name`, in parentheses, to the test case `desc` field.
 `esid` | see the general definition of the [`esid` frontmatter key](#esid).
 `info` | see the general definition of the [`info` frontmatter key](#info). Each generated test will have `info` that is the concatenation of the test template `info` field and the test case `info` field.