From cc1768e122d1583c884bc0cf9b8699aa7393bbac Mon Sep 17 00:00:00 2001 From: Dino Maric Date: Tue, 4 May 2021 20:33:06 +0200 Subject: [PATCH] Few documentations fixes. [ci skip] [changelog skip] (#2619) Sanitizing docs on few places. Ain't much. But, it's honest work :). --- docs/deployment.md | 2 +- docs/plugins.md | 2 +- docs/systemd.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/deployment.md b/docs/deployment.md index 84ebfcfb31..64b236dbe6 100644 --- a/docs/deployment.md +++ b/docs/deployment.md @@ -16,7 +16,7 @@ Welcome back! ## Single vs Cluster mode -Puma was originally conceived as a thread-only webserver, but grew the ability to +Puma was originally conceived as a thread-only web server, 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 diff --git a/docs/plugins.md b/docs/plugins.md index 8df0877a0f..985a6817f5 100644 --- a/docs/plugins.md +++ b/docs/plugins.md @@ -34,5 +34,5 @@ functionality to augment puma. `config` runs when the server is being configured and is passed a `Puma::DSL` object that can be used to add additional configuration. -Any public methods in `Puma::Plugin` are the public API that any plugin may +Any public methods in [`Puma::Plugin`](../lib/puma/plugin.rb) are the public API that any plugin may use. diff --git a/docs/systemd.md b/docs/systemd.md index 95920c0c58..4c749b1f9d 100644 --- a/docs/systemd.md +++ b/docs/systemd.md @@ -8,7 +8,7 @@ useful features for running Puma in production. ## Service Configuration Below is a sample puma.service configuration file for systemd, which -can be copied or symlinked to /etc/systemd/system/puma.service, or if +can be copied or symlinked to `/etc/systemd/system/puma.service`, or if desired, using an application or instance specific name. Note that this uses the systemd preferred "simple" type where the