Hacktoberfest spam grammar nitpciks

puma · Oct 1, 2020 · 0d354a4 · 0d354a4
1 parent de63226
commit 0d354a4
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 5 deletions.
diff --git a/docs/deployment.md b/docs/deployment.md
@@ -1,4 +1,4 @@
-# Deployment engineering for puma
+# Deployment engineering for Puma
 
 Puma is software that is expected to be run in a deployed environment eventually.
 You can certainly use it as your dev server only, but most people look to use
@@ -7,20 +7,19 @@ it in their production deployments as well.
 To that end, this is meant to serve as a foundation of wisdom how to do that
 in a way that increases happiness and decreases downtime.
 
-## Specifying puma
+## Specifying Puma
 
 Most people want to do this by putting `gem "puma"` into their Gemfile, so we'll
 go ahead and assume that. Go add it now... we'll wait.
 
-
 Welcome back!
 
 ## Single vs Cluster mode
 
 Puma was originally conceived as a thread-only webserver, but grew the ability to
 also use processes in version 2.
 
-To run puma in single mode (e.g. for a development environment) you will need to
+To run `puma` in single mode (e.g. for a development environment) you will need to
 set the number of workers to 0, anything above will run in cluster mode.
 
 Here are some rules of thumb for cluster mode:

diff --git a/docs/systemd.md b/docs/systemd.md
@@ -76,7 +76,7 @@ pass the `--keep-file-descriptors` flag. `bundle exec` can be avoided by using a
 `puma` executable generated by `bundle binstubs puma`. This is tracked in
 [#1499].
 
-**Note:** Socket activation doesn't currently work on jruby. This is
+**Note:** Socket activation doesn't currently work on JRuby. This is
 tracked in [#1367].
 
 To use socket activation, configure one or more `ListenStream` sockets