README.md in object_shadow-1.1.0 vs README.md in object_shadow-1.1.1
- old
+ new
@@ -1,14 +1,14 @@
-# Object#shadow [![[version]](https://badge.fury.io/rb/object_shadow.svg)](https://badge.fury.io/rb/object_shadow) [![[travis]](https://travis-ci.org/janlelis/object_shadow.svg)](https://travis-ci.org/janlelis/object_shadow)
+# Object#shadow [![[version]](https://badge.fury.io/rb/object_shadow.svg)](https://badge.fury.io/rb/object_shadow) [![[ci]](https://github.com/janlelis/object_shadow/workflows/Test/badge.svg)](https://github.com/janlelis/object_shadow/actions?query=workflow%3ATest)
Have you ever been [confused by some of Ruby's meta-programming methods?](https://idiosyncratic-ruby.com/25-meta-methodology.html)
If your answer is *Yes*, you have come to the right place:
-With **shadow**, every Ruby object has a shadow which encapsulates a clean API to access the object's variables and methods.
+With **shadow**, every Ruby object has a shadow which provides a clean API to access the object's variables and methods.
Never again you will have to do the `x.methods - Object.methods` trick to get a meaningful method list.
## Setup
@@ -202,8 +202,8 @@
Requires the following gems: **paint**, **wirb**, **io-console**
## J-_-L
-Copyright (C) 2019 Jan Lelis <https://janlelis.com>. Released under the MIT license.
+Copyright (C) 2019-2020 Jan Lelis <https://janlelis.com>. Released under the MIT license.
PS: This gem would not exist if the [instance gem](https://rubyworks.github.io/instance/) did not come up with the idea.