secret_string 1.0.0 → 1.0.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: '059dcb7dea1885b6f2b24c01c70567028e24cf9d4a916e607ce98d3a8ec5baab'
-  data.tar.gz: 4fc32cecd334d8cddbe7f577b5997a09c437b8d89c2d61f243db0aac137ebdb8
+  metadata.gz: adc3ac2c2e93e1c310c878c4194525a165c390dccd2d6708186f54bb1147be9a
+  data.tar.gz: d7be0b22cd44ec755337957965a140bb155c811f6223cf5264217ab591e17976
 SHA512:
-  metadata.gz: ae6503a05ddb781a1f79235630228e86c0b3c42984c43f4cbae9b331c1e7b3d456b604a523b3d4123de44b7434aea6aa4ec1c70e24410ac941d6481f7100de0c
-  data.tar.gz: 7725fe9c2bc7c17276b380ad75d68587958d1fcc6efaa1c8ed1d2591c971b91e8832966d745380933b309524ef8981409af04dd73ef59564aa8d1b0f9f9058fb
+  metadata.gz: 5b4daa15f269466054ac21521c1d5cf4f7912bcdf7d811807046a2c3f69cbca3f398381a0a9d0d205bb8778a2f59cab0ca7bbb518ece5dca243c6d358d298c90
+  data.tar.gz: d922cfba5e22b7098f7ca19501f364a8d912ef17da44d409152d79e7ad0d901a19031bdabd4fc1a2472703f5e4696510b10a4cc47863360eff1fa16547f94ace

data/CHANGELOG.md

@@ -1,3 +1,9 @@
+# [v1.0.1](https://github.com/Muriel-Salvan/secret_string/compare/v1.0.0...v1.0.1) (2021-06-30 10:46:43)
+
+### Patches
+
+* [Corrected typos in doc](https://github.com/Muriel-Salvan/secret_string/commit/46f5bb2e02ec9589818aaddf5a675820a6706b56)
+
 # [v0.0.1](https://github.com/Muriel-Salvan/secret_string/compare/...v0.0.1) (2021-06-28 16:06:53)
 
 ### Patches

data/README.md

@@ -8,15 +8,15 @@ This Rubygem gives you ways to clean sensitive data (secrets, SSH keys, password
 
 ## Install
 
-Via gem
+Via gem command line:
 
-``` bash
-$ gem install secret_string
+```bash
+gem install secret_string
 ```
 
 If using `bundler`, add this in your `Gemfile`:
 
-``` ruby
+```ruby
 gem 'secret_string'
 ```
 
@@ -63,7 +63,7 @@ end
 
 ### With the `SecretString` class
 
-If you need more control (like having a simple scope is not enough), you can directly use the `SecureString` class to protect your strings.
+If you need more control (like having a simple scope is not enough), you can directly use the `SecretString` class to protect your strings.
 If you do so, don't forget to call the `erase` method to clean their data, and make sure you didn't clone the secret in other variables.
 
 Example:
@@ -102,7 +102,7 @@ puts "My secret after being erased is #{my_secret}"
 # => My secret after being erased is
 ```
 
-The `erase` and `to_unprotected` methods have also been added to the core String class so that you can treat both `String` and `SecretString` easily within your code logic (no need to plague your code with `if str.is_a?(SecureString)`). Those methods won't do or change anything to the normal Ruby Strings.
+The `erase` and `to_unprotected` methods have also been added to the core String class so that you can treat both `String` and `SecretString` easily within your code logic (no need to plague your code with `if str.is_a?(SecretString)`). Those methods won't do or change anything to the normal Ruby Strings.
 
 Example:
 ```ruby

data/lib/secret_string/version.rb

@@ -1,5 +1,5 @@
 class SecretString
 
-  VERSION = '1.0.0'
+  VERSION = '1.0.1'
 
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: secret_string
 version: !ruby/object:Gem::Version
-  version: 1.0.0
+  version: 1.0.1
 platform: ruby
 authors:
 - Muriel Salvan
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2021-06-28 00:00:00.000000000 Z
+date: 2021-06-30 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rspec
@@ -72,9 +72,9 @@ email:
 executables: []
 extensions: []
 extra_rdoc_files:
-- CHANGELOG.md
-- LICENSE.md
 - README.md
+- LICENSE.md
+- CHANGELOG.md
 files:
 - CHANGELOG.md
 - LICENSE.md