From 3714a5e137fd12970166e8e1e45ce3ad58d0d74a Mon Sep 17 00:00:00 2001 From: Alexander Momchilov Date: Thu, 12 Dec 2024 17:04:09 -0500 Subject: [PATCH] Add syntax highlighting to MarkDown code blocks --- CONTRIBUTING.md | 4 ++-- README.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 5c3256948..366b484ba 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -113,9 +113,9 @@ Also `have_constant`, `have_private_instance_method`, `have_singleton_method`, e } ``` -##### should_not raise_error +##### `should_not raise_error` -**To avoid!** Instead, use an expectation testing what the code in the lambda does. +**Avoid this!** Instead, use an expectation testing what the code in the lambda does. If an exception is raised, it will fail the example anyway. ```ruby diff --git a/README.md b/README.md index 964efbec4..42d116206 100644 --- a/README.md +++ b/README.md @@ -44,7 +44,7 @@ For *testing* the development version of a Ruby implementation, one should alway Also, this repository doesn't always contain the latest spec changes from MRI (it's synchronized monthly), and does not contain tags (specs marked as failing on that Ruby implementation). Running specs on a Ruby implementation can be done with: -``` +```console $ cd ruby_implementation/spec/ruby # Add ../ruby_implementation/bin in PATH, or pass -t /path/to/bin/ruby $ ../mspec/bin/mspec