gemstash 2.1.0 → 2.2.1

data/lib/gemstash/man/gemstash-private-gems.7

@@ -1,16 +1,31 @@
-.\" Automatically generated by Pandoc 2.5
+<!-- Automatically generated by Pandoc -->
+.\" Automatically generated by Pandoc 3.0.1
 .\"
-.TH "gemstash\-private\-gems" "7" "October 8, 2015" "" ""
+.\" Define V font for inline verbatim, using C font in formats
+.\" that render this, and otherwise B font.
+.ie "\f[CB]x\f[]"x" \{\
+. ftr V B
+. ftr VI BI
+. ftr VB B
+. ftr VBI BI
+.\}
+.el \{\
+. ftr V CR
+. ftr VI CI
+. ftr VB CB
+. ftr VBI CBI
+.\}
+.TH "gemstash-private-gems" "7" "October 8, 2015" "" ""
 .hy
-.SH PRIVATE GEMS
+.SH Private Gems
 .PP
 Stashing private gems in your Gemstash server requires a bit of
 additional setup.
-If you haven\[cq]t read through the Quickstart
-Guide (../readme.md#quickstart-guide), you should do that first.
+If you haven\[cq]t read through the Quickstart Guide, you should do that
+first.
 By the end of this guide, you will be able to interact with your
 Gemstash server to store and retrieve your private gems.
-.SS AUTHORIZING
+.SS Authorizing
 .PP
 \f[B]IMPORTANT NOTE:\f[R] Do not use the actual key value in this
 document, otherwise your Gemstash server will be vulnerable to anyone
@@ -20,7 +35,7 @@ running the commands.
 .PP
 In order to push a gem to your Gemstash server, you need to first create
 an API key.
-Utilize the \f[C]gemstash authorize\f[R] command to create the API key:
+Utilize the \f[V]gemstash authorize\f[R] command to create the API key:
 .IP
 .nf
 \f[C]
@@ -29,16 +44,16 @@ Your new key is: e374e237fdf5fa5718d2a21bd63dc911
 \f[R]
 .fi
 .PP
-This new key can \f[C]push\f[R], \f[C]yank\f[R], and \f[C]fetch\f[R]
+This new key can \f[V]push\f[R], \f[V]yank\f[R], and \f[V]fetch\f[R]
 gems from your Gemstash server.
-Run \f[C]gemstash authorize\f[R] with just the permissions you want to
+Run \f[V]gemstash authorize\f[R] with just the permissions you want to
 limit what the key will be allowed to do.
 You can similarly update a specific key by providing it via the
-\f[C]\-\-key\f[R] option:
+\f[V]--key\f[R] option:
 .IP
 .nf
 \f[C]
-$ gemstash authorize push yank \-\-key e374e237fdf5fa5718d2a21bd63dc911
+$ gemstash authorize push yank --key e374e237fdf5fa5718d2a21bd63dc911
 \f[R]
 .fi
 .PP
@@ -49,7 +64,7 @@ all private gem interactions:
 .IP
 .nf
 \f[C]
-$ gemstash authorize \-\-key e374e237fdf5fa5718d2a21bd63dc911
+$ gemstash authorize --key e374e237fdf5fa5718d2a21bd63dc911
 \f[R]
 .fi
 .PP
@@ -62,7 +77,7 @@ file:
 .IP
 .nf
 \f[C]
-$ mkdir \-p \[ti]/.gem
+$ mkdir -p \[ti]/.gem
 $ touch \[ti]/.gem/credentials
 $ chmod 0600 \[ti]/.gem/credentials
 \f[R]
@@ -74,15 +89,15 @@ Add your new key to credentials such that it looks something like this
 .nf
 \f[C]
 # \[ti]/.gem/credentials
-\-\-\-
+---
 :test_key: e374e237fdf5fa5718d2a21bd63dc911
 \f[R]
 .fi
 .PP
-The name \f[C]test_key\f[R] can be anything you want, but you will need
+The name \f[V]test_key\f[R] can be anything you want, but you will need
 to remember it and use it again later in this guide for the
-\f[C]\-\-key\f[R] option.
-.SS CREATING A TEST GEM
+\f[V]--key\f[R] option.
+.SS Creating a Test Gem
 .PP
 You\[cq]ll need a test gem before you can play with private gems on your
 Gemstash server.
@@ -91,7 +106,7 @@ You can start by instantiating a test gem via Bundler:
 .IP
 .nf
 \f[C]
-$ bundle gem private\-example
+$ bundle gem private-example
 \f[R]
 .fi
 .PP
@@ -101,14 +116,14 @@ Once you\[cq]ve built the gem, you will be ready to push the new gem.
 .IP
 .nf
 \f[C]
-$ cd private\-example
+$ cd private-example
 $ rake build
 \f[R]
 .fi
 .PP
 You will now have a gem at
-\f[C]private\-example/pkg/private\-example\-0.1.0.gem\f[R].
-.SS PUSHING
+\f[V]private-example/pkg/private-example-0.1.0.gem\f[R].
+.SS Pushing
 .PP
 If your Gemstash server isn\[cq]t running, go ahead and start it:
 .IP
@@ -122,19 +137,19 @@ Push your test gem using Rubygems:
 .IP
 .nf
 \f[C]
-$ gem push \-\-key test_key \-\-host http://localhost:9292/private pkg/private\-example\-0.1.0.gem
+$ gem push --key test_key --host http://localhost:9292/private pkg/private-example-0.1.0.gem
 \f[R]
 .fi
 .PP
-The \f[C]/private\f[R] portion of the \f[C]\-\-host\f[R] option tells
+The \f[V]/private\f[R] portion of the \f[V]--host\f[R] option tells
 Gemstash you are interacting with the private gems.
 Gemstash will not let you push, or yank from anything except
-\f[C]/private\f[R].
-.SS BUNDLING
+\f[V]/private\f[R].
+.SS Bundling
 .PP
 Once your gem is pushed to your Gemstash server, you are ready to bundle
 it.
-Create a \f[C]Gemfile\f[R] and specify the gem.
+Create a \f[V]Gemfile\f[R] and specify the gem.
 You will probably want to wrap the private gem in a source block, and
 let the rest of Gemstash handle all other gems:
 .IP
@@ -145,12 +160,12 @@ source \[dq]http://localhost:9292\[dq]
 gem \[dq]rubywarrior\[dq]
 
 source \[dq]http://localhost:9292/private\[dq] do
-  gem \[dq]private\-example\[dq]
+  gem \[dq]private-example\[dq]
 end
 \f[R]
 .fi
 .PP
-Notice that the Gemstash server points to \f[C]/private\f[R] again when
+Notice that the Gemstash server points to \f[V]/private\f[R] again when
 installing your private gem.
 Go ahead and bundle to install your new private gem:
 .IP
@@ -159,34 +174,34 @@ Go ahead and bundle to install your new private gem:
 $ bundle
 \f[R]
 .fi
-.SS YANKING
+.SS Yanking
 .PP
 If you push a private gem by accident, you can yank the gem with
 Rubygems:
 .IP
 .nf
 \f[C]
-$ RUBYGEMS_HOST=http://localhost:9292/private gem yank \-\-key test_key private\-example \-\-version 0.1.0
+$ RUBYGEMS_HOST=http://localhost:9292/private gem yank --key test_key private-example --version 0.1.0
 \f[R]
 .fi
 .PP
-Like with pushing, the \f[C]/private\f[R] portion of the host option
+Like with pushing, the \f[V]/private\f[R] portion of the host option
 tells Gemstash you are interacting with private gems.
-Gemstash will only let you yank from \f[C]/private\f[R].
-Unlike pushing, Rubygems doesn\[cq]t support \f[C]\-\-host\f[R] for yank
-(yet), so you need to specify the host via the \f[C]RUBYGEMS_HOST\f[R]
+Gemstash will only let you yank from \f[V]/private\f[R].
+Unlike pushing, Rubygems doesn\[cq]t support \f[V]--host\f[R] for yank
+(yet), so you need to specify the host via the \f[V]RUBYGEMS_HOST\f[R]
 environment variable.
-.SS PROTECTED FETCHING
+.SS Protected Fetching
 .PP
 By default, private gems and specs can be accessed without
 authentication.
 .PP
 Private gems often require protected fetching.
 For backwards compatibility this is disabled by default, but can be
-enabled via \f[C]$ gemstash setup\f[R] command.
+enabled via \f[V]$ gemstash setup\f[R] command.
 .PP
 When protected fetching is enabled API keys with the permissions
-\f[C]all\f[R] or \f[C]fetch\f[R] can be used to download gems and specs.
+\f[V]all\f[R] or \f[V]fetch\f[R] can be used to download gems and specs.
 .PP
 On the Bundler side, there are a few ways to configure credentials for a
 given gem source:
@@ -195,7 +210,7 @@ Add credentials globally:
 .IP
 .nf
 \f[C]
-$ bundle config my\-gemstash.dev api_key
+$ bundle config my-gemstash.dev api_key
 \f[R]
 .fi
 .PP
@@ -203,7 +218,7 @@ Add credentials in Gemfile:
 .IP
 .nf
 \f[C]
-source \[dq]https://api_key\[at]my\-gemstash.dev\[dq]
+source \[dq]https://api_key\[at]my-gemstash.dev\[dq]
 \f[R]
 .fi
 .PP
@@ -220,7 +235,7 @@ $ export BUNDLE_MYGEMSTASH__DEV=api_key
 .fi
 .PP
 Behind the scene, Bundler will pick up the ENV var according to the host
-name (e.g.\ mygemstash.dev) and add to \f[C]URI.userinfo\f[R] for making
+name (e.g.\ mygemstash.dev) and add to \f[V]URI.userinfo\f[R] for making
 requests.
 .PP
 The API key is treated as a HTTP Basic Auth username and any HTTP Basic

data/lib/gemstash/man/gemstash-private-gems.7.txt

@@ -2,30 +2,32 @@ gemstash-private-gems(7)			      gemstash-private-gems(7)
 
 
 
-1mPRIVATE GEMS0m
-       Stashing	 private  gems in your Gemstash server requires a bit of addi-
-       tional setup.   If  you	haven't	 read  through	the  Quickstart	 Guide
-       (../readme.md#quickstart-guide),	 you should do that first.  By the end
-       of this guide, you will be able to interact with your  Gemstash	server
-       to store and retrieve your private gems.
-
-   1mAUTHORIZING0m
+<!-- Automatically generated by Pandoc -->
+
+1mPrivate Gems0m
+       Stashing  private  gems in your Gemstash server requires a bit of addi-
+       tional setup.  If you haven't read through the  Quickstart  Guide,  you
+       should  do  that  first.  By the end of this guide, you will be able to
+       interact with your Gemstash server to store and retrieve  your  private
+       gems.
+
+   1mAuthorizing0m
        1mIMPORTANT  NOTE: 22mDo not use the actual key value in this document, oth-
        erwise your Gemstash server will be vulnerable to anyone who  wants  to
        try to use the key against your server.	Instead of the key value here,
        use whatever key is generated from running the commands.
 
        In order to push a gem to your Gemstash server, you need to first  cre-
-       ate  an	API key.  Utilize the gemstash authorize command to create the
+       ate  an	API key.  Utilize the 1mgemstash authorize 22mcommand to create the
        API key:
 
 	      $ gemstash authorize
 	      Your new key is: e374e237fdf5fa5718d2a21bd63dc911
 
-       This new key can push, yank, and fetch gems from your Gemstash  server.
-       Run gemstash authorize with just the permissions you want to limit what
+       This new key can 1mpush22m, 1myank22m, and 1mfetch 22mgems from your Gemstash  server.
+       Run 1mgemstash authorize 22mwith just the permissions you want to limit what
        the key will be allowed to do.  You can similarly update a specific key
-       by providing it via the --key option:
+       by providing it via the 1m--key 22moption:
 
 	      $ gemstash authorize push yank --key e374e237fdf5fa5718d2a21bd63dc911
 
@@ -51,13 +53,13 @@ gemstash-private-gems(7)			      gemstash-private-gems(7)
 	      ---
 	      :test_key: e374e237fdf5fa5718d2a21bd63dc911
 
-       The name test_key can be anything you want, but you will need to remem-
-       ber it and use it again later in this guide for the --key option.
+       The name 1mtest_key 22mcan be anything you want, but you will need to remem-
+       ber it and use it again later in this guide for the 1m--key 22moption.
 
-   1mCREATING A TEST GEM0m
+   1mCreating a Test Gem0m
        You'll need a test gem before you can play with private	gems  on  your
-       Gemstash server.	 If you have a gem you can use, move along to the next
-       section.	 You can start by instantiating a test gem via Bundler:
+       Gemstash server.  If you have a gem you can use, move along to the next
+       section.  You can start by instantiating a test gem via Bundler:
 
 	      $ bundle gem private-example
 
@@ -68,10 +70,10 @@ gemstash-private-gems(7)			      gemstash-private-gems(7)
 	      $ cd private-example
 	      $ rake build
 
-       You  will  now  have   a	  gem	at   private-example/pkg/private-exam-
-       ple-0.1.0.gem.
+       You  will  now  have   a   gem	at   1mprivate-example/pkg/private-exam-0m
+       1mple-0.1.0.gem22m.
 
-   1mPUSHING0m
+   1mPushing0m
        If your Gemstash server isn't running, go ahead and start it:
 
 	      $ gemstash start
@@ -80,13 +82,13 @@ gemstash-private-gems(7)			      gemstash-private-gems(7)
 
 	      $ gem push --key test_key --host http://localhost:9292/private pkg/private-example-0.1.0.gem
 
-       The /private portion of the --host option tells Gemstash you are inter-
+       The 1m/private 22mportion of the 1m--host 22moption tells Gemstash you are inter-
        acting with the private gems.  Gemstash will not let you push, or  yank
-       from anything except /private.
+       from anything except 1m/private22m.
 
-   1mBUNDLING0m
+   1mBundling0m
        Once  your gem is pushed to your Gemstash server, you are ready to bun-
-       dle it.	Create a Gemfile and specify the gem.  You will probably  want
+       dle it.	Create a 1mGemfile 22mand specify the gem.  You will probably  want
        to wrap the private gem in a source block, and let the rest of Gemstash
        handle all other gems:
 
@@ -98,34 +100,34 @@ gemstash-private-gems(7)			      gemstash-private-gems(7)
 		gem "private-example"
 	      end
 
-       Notice that the Gemstash server	points	to  /private  again  when  in-
-       stalling	 your  private	gem.   Go ahead and bundle to install your new
+       Notice that the Gemstash server	points	to  1m/private	22magain  when	in-
+       stalling  your  private	gem.   Go ahead and bundle to install your new
        private gem:
 
 	      $ bundle
 
-   1mYANKING0m
+   1mYanking0m
        If you push a private gem by  accident,	you  can  yank	the  gem  with
        Rubygems:
 
 	      $ RUBYGEMS_HOST=http://localhost:9292/private gem yank --key test_key private-example --version 0.1.0
 
-       Like  with  pushing, the /private portion of the host option tells Gem-
+       Like  with  pushing, the 1m/private 22mportion of the host option tells Gem-
        stash you are interacting with private gems.  Gemstash  will  only  let
-       you  yank  from	/private.   Unlike  pushing,  Rubygems doesn't support
-       --host for yank (yet),  so  you	need  to  specify  the	host  via  the
-       RUBYGEMS_HOST environment variable.
+       you  yank  from	1m/private22m.	 Unlike  pushing,  Rubygems doesn't support
+       1m--host 22mfor yank (yet),  so	you  need  to  specify	the  host  via	the
+       1mRUBYGEMS_HOST 22menvironment variable.
 
-   1mPROTECTED FETCHING0m
+   1mProtected Fetching0m
        By  default, private gems and specs can be accessed without authentica-
        tion.
 
        Private gems often require protected fetching.  For backwards  compati-
-       bility  this  is disabled by default, but can be enabled via $ gemstash
-       setup command.
+       bility  this  is disabled by default, but can be enabled via 1m$ gemstash0m
+       1msetup 22mcommand.
 
-       When protected fetching is enabled API keys with the permissions all or
-       fetch can be used to download gems and specs.
+       When protected fetching is enabled API keys with the permissions 1mall 22mor
+       1mfetch 22mcan be used to download gems and specs.
 
        On  the Bundler side, there are a few ways to configure credentials for
        a given gem source:
@@ -145,7 +147,7 @@ gemstash-private-gems(7)			      gemstash-private-gems(7)
 	      $ export BUNDLE_MYGEMSTASH__DEV=api_key
 
        Behind the scene, Bundler will pick up the ENV  var  according  to  the
-       host  name (e.g. mygemstash.dev) and add to URI.userinfo for making re-
+       host  name (e.g. mygemstash.dev) and add to 1mURI.userinfo 22mfor making re-
        quests.
 
        The API key is treated as a HTTP Basic Auth username and any HTTP Basic
@@ -153,4 +155,4 @@ gemstash-private-gems(7)			      gemstash-private-gems(7)
 
 
 
-				October 8, 2015	      gemstash-private-gems(7)
+				October 8, 2015       gemstash-private-gems(7)

data/lib/gemstash/man/gemstash-readme.7

@@ -1,9 +1,24 @@
-.\" Automatically generated by Pandoc 2.5
+<!-- Automatically generated by Pandoc -->
+.\" Automatically generated by Pandoc 3.0.1
 .\"
-.TH "gemstash\-readme" "7" "November 30, 2015" "" ""
+.\" Define V font for inline verbatim, using C font in formats
+.\" that render this, and otherwise B font.
+.ie "\f[CB]x\f[]"x" \{\
+. ftr V B
+. ftr VI BI
+. ftr VB B
+. ftr VBI BI
+.\}
+.el \{\
+. ftr V CR
+. ftr VI CI
+. ftr VB CB
+. ftr VBI CBI
+.\}
+.TH "gemstash-readme" "7" "November 30, 2015" "" ""
 .hy
-.SH GEMSTASH
-.SS WHAT IS GEMSTASH?
+.SH Gemstash
+.SS What is Gemstash?
 .PP
 Gemstash is both a cache for remote servers such as
 https://rubygems.org, and a private gem source.
@@ -20,7 +35,8 @@ you might want to use Gemstash.
 .PP
 Are you only using gems from https://rubygems.org, and don\[cq]t bundle
 the same gems frequently?
-Well, maybe you don\[cq]t need Gemstash\&... yet.
+Well, maybe you don\[cq]t need Gemstash\&...
+yet.
 .PP
 Gemstash is maintained by Ruby Together (https://rubytogether.org/), a
 grassroots initiative committed to supporting the critical Ruby
@@ -29,8 +45,8 @@ Contribute today as an individual (https://rubytogether.org/developers)
 or even better, as a company (https://rubytogether.org/companies), and
 ensure that Bundler, RubyGems, Gemstash, and other shared tooling is
 around for years to come.
-.SS QUICKSTART GUIDE
-.SS SETUP
+.SS Quickstart Guide
+.SS Setup
 .PP
 Gemstash is designed to be quick and painless to get set up.
 By the end of this Quickstart Guide, you will be able to bundle stashed
@@ -46,7 +62,7 @@ $ gem install gemstash
 .fi
 .PP
 After it is installed, starting Gemstash requires no additional steps.
-Simply start the Gemstash server with the \f[C]gemstash\f[R] command:
+Simply start the Gemstash server with the \f[V]gemstash\f[R] command:
 .IP
 .nf
 \f[C]
@@ -58,7 +74,7 @@ You may have noticed that the command finished quickly.
 This is because Gemstash will run the server in the background by
 default.
 The server runs on port 9292.
-.SS BUNDLING
+.SS Bundling
 .PP
 With the server running, you can bundle against it.
 Tell Bundler that you want to use Gemstash to find gems from
@@ -86,13 +102,13 @@ Now bundle:
 .IP
 .nf
 \f[C]
-$ bundle install \-\-path .bundle
+$ bundle install --path .bundle
 \f[R]
 .fi
 .PP
 Your Gemstash server has fetched the gems from https://rubygems.org and
-cached them for you! To prove this, you can disable your Internet
-connection and try again.
+cached them for you!
+To prove this, you can disable your Internet connection and try again.
 Gem files (*.gem) are cached indefinitely.
 Gem dependencies metadata are cached for 30 minutes, so if you bundle
 again before that, you can successfully bundle without an Internet
@@ -101,11 +117,11 @@ connection:
 .nf
 \f[C]
 $ # Disable your Internet first!
-$ rm \-rf Gemfile.lock .bundle
+$ rm -rf Gemfile.lock .bundle
 $ bundle
 \f[R]
 .fi
-.SS FALLING BACK TO RUBYGEMS.ORG
+.SS Falling back to rubygems.org
 .PP
 If you want to make sure that your bundling from https://rubygems.org
 still works as expected when the Gemstash server is not running, you can
@@ -126,7 +142,7 @@ This example uses a 3 second timeout:
 $ bundle config mirror.https://rubygems.org.fallback_timeout 3
 \f[R]
 .fi
-.SS STOPPING THE SERVER
+.SS Stopping the Server
 .PP
 Once you\[cq]ve finish using your Gemstash server, you can stop it just
 as easily as you started it:
@@ -142,83 +158,79 @@ from RubyGems.org directly, instead of going through Gemstash:
 .IP
 .nf
 \f[C]
-$ bundle config \-\-delete mirror.https://rubygems.org
+$ bundle config --delete mirror.https://rubygems.org
 \f[R]
 .fi
-.SS UNDER THE HOOD
+.SS Under the Hood
 .PP
 You might wonder where the gems are stored.
 After running the commands above, you will find a new directory at
-\f[C]\[ti]/.gemstash\f[R].
+\f[V]\[ti]/.gemstash\f[R].
 This directory holds all the cached and private gems.
 It also has a server log, the database, and configuration for Gemstash.
-If you prefer, you can point to a different
-directory (gemstash help customize.7).
+If you prefer, you can point to a different directory.
 .PP
 Gemstash uses SQLite (https://www.sqlite.org/) to store details about
 private gems.
-The database will be located in \f[C]\[ti]/.gemstash\f[R], however you
+The database will be located in \f[V]\[ti]/.gemstash\f[R], however you
 won\[cq]t see the database appear until you start using private gems.
-If you prefer, you can use a different
-database (gemstash help customize.7).
+If you prefer, you can use a different database.
 .PP
 Gemstash temporarily caches things like gem dependencies in memory.
 Anything cached in memory will last for 30 minutes before being
 retrieved again.
-You can use memcached (gemstash help customize.7) instead of caching in
-memory.
+You can use memcached instead of caching in memory.
 Gem files are always cached permanently, so bundling with a
-\f[C]Gemfile.lock\f[R] with all gems cached will never call out to
+\f[V]Gemfile.lock\f[R] with all gems cached will never call out to
 https://rubygems.org.
 .PP
 The server you ran is provided via Puma (http://puma.io/) and
 Rack (http://rack.github.io/), however they are not customizable at this
 point.
-.SS DEEP DIVE
+.SS Deep Dive
 .PP
 Deep dive into more subjects:
 .IP \[bu] 2
-Private gems (gemstash help private-gems.7)
+Private gems
 .IP \[bu] 2
-Multiple gem sources (gemstash help multiple-sources.7)
+Multiple gem sources
 .IP \[bu] 2
-Using Gemstash as a mirror (gemstash help mirror.7)
+Using Gemstash as a mirror
 .IP \[bu] 2
-Customizing the server (database, storage, caching, and
-more) (gemstash help customize.7)
+Customizing the server (database, storage, caching, and more)
 .IP \[bu] 2
-Deploying Gemstash (gemstash help deploy.7)
+Deploying Gemstash
 .IP \[bu] 2
-Debugging Gemstash (gemstash help debugging.7)
-.SS REFERENCE
+Debugging Gemstash
+.SS Reference
 .PP
 An anatomy of various configuration and commands:
 .IP \[bu] 2
-Configuration (gemstash help configuration.5)
+Configuration
 .IP \[bu] 2
-Authorize (gemstash help authorize.1)
+Authorize
 .IP \[bu] 2
-Start (gemstash help start.1)
+Start
 .IP \[bu] 2
-Stop (gemstash help stop.1)
+Stop
 .IP \[bu] 2
-Status (gemstash help status.1)
+Status
 .IP \[bu] 2
-Setup (gemstash help setup.1)
+Setup
 .IP \[bu] 2
-Version (gemstash help version.1)
+Version
 .PP
 To see what has changed in recent versions of Gemstash, see the
 CHANGELOG (https://github.com/rubygems/gemstash/blob/master/CHANGELOG.md).
-.SS DEVELOPMENT
+.SS Development
 .PP
-After checking out the repo, run \f[C]bin/setup\f[R] to install
+After checking out the repo, run \f[V]bin/setup\f[R] to install
 dependencies.
-Then, run \f[C]rake\f[R] to run RuboCop and the tests.
-While developing, you can run \f[C]bin/gemstash\f[R] to run Gemstash.
-You can also run \f[C]bin/console\f[R] for an interactive prompt that
+Then, run \f[V]rake\f[R] to run RuboCop and the tests.
+While developing, you can run \f[V]bin/gemstash\f[R] to run Gemstash.
+You can also run \f[V]bin/console\f[R] for an interactive prompt that
 will allow you to experiment.
-.SS CONTRIBUTING
+.SS Contributing
 .PP
 Bug reports and pull requests are welcome on GitHub at
 https://github.com/rubygems/gemstash.
@@ -227,7 +239,7 @@ collaboration, and contributors are expected to adhere to the
 Contributor
 Covenant (https://github.com/rubygems/gemstash/blob/master/CODE_OF_CONDUCT.md)
 code of conduct.
-.SS LICENSE
+.SS License
 .PP
 The gem is available as open source under the terms of the MIT
 License (http://opensource.org/licenses/MIT).