https://git.ruby-lang.org/ruby.git/commit/?id=bce0021f75

From bce0021f75eaca118c18ebb5a4fe29ede565071f Mon Sep 17 00:00:00 2001
From: Anton Rieder <1301152+aried3r@u...>
Date: Tue, 22 Jun 2021 13:15:21 +0200
Subject: [Documentation] Fix typo, formatting in `time.c`

Backticks do not result in code formatting.
---
 time.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/time.c b/time.c
index 73e3f11..12e5c0d 100644
--- a/time.c
+++ b/time.c
@@ -3458,10 +3458,10 @@ time_to_i(VALUE time) https://github.com/ruby/ruby/blob/trunk/time.c#L3458
  *  the exact number of nanoseconds since the Epoch.
  *  (IEEE 754 double has 53bit mantissa.
  *  So it can represent exact number of nanoseconds only in
- *  `2 ** 53 / 1_000_000_000 / 60 / 60 / 24 = 104.2` days.)
+ *  <tt>2 ** 53 / 1_000_000_000 / 60 / 60 / 24 = 104.2</tt> days.)
  *  When Ruby uses a nanosecond-resolution clock function,
  *  such as +clock_gettime+ of POSIX, to obtain the current time,
- *  Time#to_f can lost information of a Time object created with +Time.now+.
+ *  Time#to_f can lose information of a Time object created with +Time.now+.
  */
 
 static VALUE
-- 
cgit v1.1


--
ML: ruby-changes@q...
Info: http://www.atdot.net/~ko1/quickml/