We want the information in Ruby-Doc Learn to be accurate and reliable. However, programming languages, libraries and services are constantly changing so that articles based on current information may also eventually become inaccurate or outdated.
We encourage you to submit good supporting evidence when reporting an error.
Reporting an Error
You can send us an email at contact@ruby-doc.org with the subject line “Correction: [article title]”. Please provide:
- The URL of the article
- The section or code example where you think there is an error
- A brief explanation of why you believe there is an error
- Any additional information you have about how to fix the problem
- Evidence that supports your claim (test results, screenshots etc.)
- Information about which version of Ruby, Rails, library or service you used
Reports that provide enough detail for us to reproduce or verify the issue are especially helpful.
Handling Corrections
We determine whether a correction request is minor or material based upon its impact on the reader. Minor corrections might involve correcting typographical errors such as misspellings, punctuation or capitalization errors in wording. Those types of corrections are usually simple to complete and do not need a large correction notice. Material corrections include errors in code or instructions, factual inaccuracies, compatibility issues and misleading conclusions. When a material correction is needed, we may add an editor’s note explaining what changed and update the article’s last-modified date.
It is possible that a warning message may be posted instead if the article is deemed to be substantially unreliable or likely to mislead readers until the article is reviewed. Articles that cannot be corrected responsibly may be removed from public viewing altogether.
Updates Are Not Always Corrections
Articles that once accurately represented information may no longer reflect reality after a new version of Ruby, Rails, library or service has been released. It is possible that we will mark such articles as outdated or rewrite them to represent new versions of these products. Alternatively we may continue to maintain old versions of articles documenting older versions of software.
Rewritten articles should not be presented as if they were originally published without an updated date or editorial note.
Retraction/Removal of Content
Ruby-Doc Learn reserves the right to remove or retract content that involves serious inaccuracies; plagiarism; fabricated authorship; undisclosed commercial influence and other breaches of our editorial policy. Where appropriate, a notice will be left behind to explain why the article has been taken down.
We review all legitimate submissions. We may not be able to respond individually to automated, abusive or unsupported submissions.
Last updated: 3 September 2026