From c0572a05dafffa5bbd15a8cd7a7f8d4760adb8b5 Mon Sep 17 00:00:00 2001
From: Peter Dunkley <peter.dunkley@crocodilertc.net>
Date: Wed, 14 Aug 2013 19:53:44 +0100
Subject: [PATCH] More tidying of EL docs

---
 el/README.md | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/el/README.md b/el/README.md
index 03ef52080..e0d533457 100644
--- a/el/README.md
+++ b/el/README.md
@@ -33,9 +33,12 @@ To build the RPMs you need all of the packages listed in the Manual Compilation
 To build the RPMs:
 - Checkout (clone) the Git repository
 - Create the `~/rpmbuild/SOURCES` directory
-- Create a tar archive.  For example, from within the cloned directory you can use `git archive --output ~/rpmbuild/SOURCES/ngcp-mediaproxy-ng-<version>.tar.gz --prefix=ngcp-mediaproxy-ng-<version>/ master` (where <version> is the version number of the master branch)
+- Create a tar archive.  For example, from within the cloned directory you can
+  use
+  `git archive --output ~/rpmbuild/SOURCES/ngcp-mediaproxy-ng-<version number>.tar.gz --prefix=ngcp-mediaproxy-ng-<version number>/ master`
+  where `<version number>` is the version number of the master branch
 - Build the RPMs. For example,
-   `rpmbuild -ta ~/rpmbuild/SOURCES/ngcp-mediaproxy-ng-<version>.tar.gz`
+   `rpmbuild -ta ~/rpmbuild/SOURCES/ngcp-mediaproxy-ng-<version number>.tar.gz`
 
 Once the build has completed the binary RPMs will be in `~/rpmbuild/RPMS`.