From 12a9bea66133a5cb121a33a7c05dcf9f9be4e21f Mon Sep 17 00:00:00 2001 From: Jinpeng Date: Fri, 10 Jan 2025 18:13:06 -0500 Subject: [PATCH] fix markdown format --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index cc0678930c0..7a3dc1dd245 100644 --- a/README.md +++ b/README.md @@ -95,8 +95,8 @@ Planned Release Schedule In general, use panics for bad states that are unreachable, unrecoverable or harmful. For those caused by invalid user input, however, we prefer to report that invalidity gracefully as an error result instead of panicking. In general, invalid input should result -in an `Error` as soon as possible. It *is* ok for code paths after validation to assume validation has -already occurred and panic if not. See [this ticket] for more nuances. +in an `Error` as soon as possible. It _is_ ok for code paths after validation to assume +validation has already occurred and panic if not. See [this ticket] for more nuances. [this ticket]: https://github.com/apache/arrow-rs/issues/6737