From a9d9ca76b16ce9f90487f8b4f78ddbef708d4995 Mon Sep 17 00:00:00 2001
From: Runxi Yu
Date: Fri, 6 Mar 2026 03:11:45 +0800
Subject: README: Software reproduction language

---
 README.md | 25 ++++++++++++-------------
 1 file changed, 12 insertions(+), 13 deletions(-)

(limited to 'README.md')

diff --git a/README.md b/README.md
index 52945e23..0a2376b8 100644
--- a/README.md
+++ b/README.md
@@ -125,19 +125,18 @@ Mainly tests the packfile object reader.
 
 ## Reporting bugs
 
-All problem/bug reports should include a reproduction recipe in form
-of a Go program which starts out with an empty repository and runs a
-series of Furgit functions/methods and/or Git commands to trigger the
-problem, be it a crash or some other undesirable behavior.
-
-Please take this request very seriously; Ask for help with writing your
-regression test before asking for your problem to be fixed. Time invested in
-writing a regression test saves time wasted on back-and-forth discussion about
-how the problem can be reproduced. A regression test will need to be written in
-any case to verify a fix and prevent the problem from resurfacing.
-
-If writing an automated test really turns out to be impossible, please
-explain in very clear terms how the problem can be reproduced.
+Bug reports ideally include a reproduction recipe: a Go program which starts
+out with an empty repository and calls Furgit and/or Git commands to trigger
+undesirable behavior.
+
+Please ask for help with writing your regression test before asking for your
+problem to be fixed. Time invested in writing a regression test saves time
+wasted on back-and-forth discussion about how the problem can be reproduced. A
+regression test will need to be written in any case to verify a fix and prevent
+the problem from resurfacing.
+
+If writing an automated test really turns out to be impossible, please explain
+in very clear terms how the problem can be reproduced.
 
 ## License
 
-- 
cgit v1.3.1-10-gc9f91