From 4d656d01380096014493a78de2261bc7f1e41e91 Mon Sep 17 00:00:00 2001
From: Dmitry Shibanov <dmitry-shibanov@github.com>
Date: Mon, 15 Feb 2021 10:22:04 +0300
Subject: [PATCH] work on resolving comments

---
 README.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/README.md b/README.md
index ae33eb2..db93c23 100644
--- a/README.md
+++ b/README.md
@@ -88,9 +88,9 @@ jobs:
 
 ### Extra setup for pom.xml:
 
-Maven GPG Plugin configuration in pom.xml file should contain the following structure to avoid possible issues like `Inappropriate ioctl for device` or `gpg: signing failed: No such file or directory`:
+The Maven GPG Plugin configuration in the pom.xml file should contain the following structure to avoid possible issues like `Inappropriate ioctl for device` or `gpg: signing failed: No such file or directory`:
 
-```
+```xml
 <configuration>
   <!-- Prevent gpg from using pinentry programs -->
   <gpgArguments>
@@ -99,7 +99,7 @@ Maven GPG Plugin configuration in pom.xml file should contain the following stru
   </gpgArguments>
 </configuration>
 ```
-GPG 2.1 requires `--pinentry-mode` to be set to `loopback` in order to pick up `gpg.passphrase` value defined in Maven `settings.xml`
+GPG 2.1 requires `--pinentry-mode` to be set to `loopback` in order to pick up the `gpg.passphrase` value defined in Maven `settings.xml`.
 
 ### Yaml example:
 ```yaml