From 31dc65b2750e15e5a55a87e87e0d41e935ec7d3a Mon Sep 17 00:00:00 2001 From: stomar Date: Wed, 12 Dec 2018 22:04:48 +0000 Subject: [PATCH] string.c: [DOC] fix typos git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66375 b2dd03c8-39d4-4d8f-98ff-823fe69b080e --- string.c | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/string.c b/string.c index 4fb2c04ad9..71afc98ba5 100644 --- a/string.c +++ b/string.c @@ -9237,17 +9237,17 @@ rb_str_oct(VALUE str) * * So-called "traditional" usage of crypt(3) is very * very very weak. According to its manpage, Linux's traditional * crypt(3) output has only 2**56 variations; too - * easy to blute force today. And this is the default behaviour. + * easy to brute force today. And this is the default behaviour. * * * In order to make things robust some OSes implement so-called * "modular" usage. To go through, you have to do a complex * build-up of the salt_str parameter, by hand. * Failure in generation of a proper salt string tends not to - * yield any errors; typo in parameters are normally not + * yield any errors; typos in parameters are normally not * detectable. * - * * For instance, in the following example, second invocation - * of String#crypt is wrong; it has typo in + * * For instance, in the following example, the second invocation + * of String#crypt is wrong; it has a typo in * "round=" (lacks "s"). However the call does not fail and * something unexpected is generated. * @@ -9271,7 +9271,7 @@ rb_str_oct(VALUE str) * * If for some reason you cannot migrate to other secure contemporary * password hashing algorithms, install the string-crypt gem and - * requiire 'string/crypt' to continue using it. + * require 'string/crypt' to continue using it. */ static VALUE