From e3571a2bb4c433e0598070074c17935b49f569d9 Mon Sep 17 00:00:00 2001
From: Santiago Lo Coco <santilococo.01@gmail.com>
Date: Thu, 3 Mar 2022 11:11:31 -0300
Subject: [PATCH] Update README.md

---
 README.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/README.md b/README.md
index 5ac18ab..db3b80f 100644
--- a/README.md
+++ b/README.md
@@ -4,19 +4,19 @@ GitHub action to build a package, analyze it with `namcap`, and output the packa
 This action supports PKGBUILDs that have AUR dependencies.
 
 ## Table of contents
-  - [Inputs and outputs <a name="inputs-and-outputs-"></a>](#inputs-and-outputs--)
+  - [Inputs and outputs <a name="inputs-and-outputs-"></a>](#inputs-and-outputs-)
   - [Usage <a name="usage"></a>](#usage-)
   - [Contributing <a name="contributing"></a>](#contributing-)
   - [License <a name="license"></a>](#license-)
 
 ## Inputs and outputs <a name="inputs-and-outputs-"></a>
 ### Inputs:
-* `pkgDir`: PKGBUILD directory relative path.
+* `pkgDir`: relative path to the PKGBUILD directory.
 * `gpgPublicKey`: GPG public key that will be used to sign packages.
 * `gpgPrivateKey`: GPG private key.
-* `gpgPassphrase`: The GPG passphrase for the `gpgPrivateKey`.
+* `gpgPassphrase`: GPG passphrase of `gpgPrivateKey`.
 
-It is recommended that you store the `gpgPrivateKey` and the `gpgPassphrase` as secrets (see [Usage <a name="usage"></a>](#usage-)).
+It is recommended to store `gpgPrivateKey` and `gpgPassphrase` as secrets (see [Usage](#usage-)).
 
 None of these inputs are required.