Merge branch 'master' into patch-1

Author: kenyonj

.github/main.workflow

@@ -3,22 +3,22 @@ GEM
   specs:
     ast (2.4.0)
     fastimage (2.1.5)
-    jaro_winkler (1.5.2)
+    jaro_winkler (1.5.3)
     minitest (5.11.3)
     parallel (1.17.0)
     parser (2.6.3.0)
       ast (~> 2.4.0)
     rainbow (3.0.0)
     rake (12.3.2)
-    rubocop (0.71.0)
+    rubocop (0.72.0)
       jaro_winkler (~> 1.5.1)
       parallel (~> 1.10)
       parser (>= 2.6)
       rainbow (>= 2.2.2, < 4.0)
       ruby-progressbar (~> 1.7)
       unicode-display_width (>= 1.4.0, < 1.7)
-    rubocop-performance (1.3.0)
-      rubocop (>= 0.68.0)
+    rubocop-performance (1.4.0)
+      rubocop (>= 0.71.0)
     ruby-progressbar (1.10.1)
     safe_yaml (1.0.5)
     unicode-display_width (1.6.0)

Gemfile.lock

@@ -17,6 +17,7 @@ items:
  - zedapp/zed
  - Microsoft/vscode
  - zyedidia/micro
+ - neoedmund/neoeedit
 display_name: Text editors
 created_by: leereilly
 image: text-editors.png

collections/text-editors/index.md

@@ -0,0 +1,12 @@
+---
+aliases: rfc-7519
+created_by: M. Jones, J. Bradley, N. Sakimura
+display_name: JSON Web Tokens
+released: May 2015
+short_description: JSON Web Tokens are an open, industry standard RFC 7519 method for representing claims securely between two parties.
+topic: jwt
+related: json, jwt-token, jwt-tokens, jwt-auth
+url: https://www.rfc-editor.org/info/rfc7519
+wikipedia_url: https://en.wikipedia.org/wiki/JSON_Web_Token
+---
+JSON Web Token (JWT) is a compact, URL-safe means of representing claims to be transferred between two parties.  The claims in a JWT are encoded as a JSON object that is used as the payload of a JSON Web Signature (JWS) structure or as the plaintext of a JSON Web Encryption (JWE) structure, enabling the claims to be digitally signed or integrity protected with a Message Authentication Code (MAC) and/or encrypted.