Author: kwin
Date: Thu Jan 21 16:53:48 2016
New Revision: 1726021

URL: http://svn.apache.org/viewvc?rev=1726021&view=rev
Log:
try to fix indentation

Modified:
    sling/site/trunk/content/documentation/development/release-management.mdtext

Modified: 
sling/site/trunk/content/documentation/development/release-management.mdtext
URL: 
http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/development/release-management.mdtext?rev=1726021&r1=1726020&r2=1726021&view=diff
==============================================================================
--- 
sling/site/trunk/content/documentation/development/release-management.mdtext 
(original)
+++ 
sling/site/trunk/content/documentation/development/release-management.mdtext 
Thu Jan 21 16:53:48 2016
@@ -319,16 +319,18 @@ Considering that you are using a \*nix s
 
         $ gpg --gen-key
 
-    When gpg asks for e-mail linked the key you *MUST USE* the 
<committer>@apache.org one
-    When gpg asks for comment linked the key you *SHOULD USE* "CODE SIGNING 
KEY"
+    When gpg asks for e-mail linked the key you *MUST USE* the 
&lt;committer&gt;@apache.org one. When gpg asks for comment linked the key you 
*SHOULD USE* "CODE SIGNING KEY"
 
 1. Add the key to 
[https://people.apache.org/keys/group/sling.asc](https://people.apache.org/keys/group/sling.asc)
 by doing the following steps
+
     1. Type the following command replacing the word `<e-mail>` with your 
Apache's one (&lt;committer&gt;@apache.org) to get the key signature
     
             $ gpg --fingerprint <e-mail>
             
        The key signature is in the output following the `Key fingerprint = `
+       
     1. Add the key signature into the field 'OpenPGP Public Key Primary 
Fingerprint' in your profile at [https://id.apache.org](https://id.apache.org)
+    
     1. You are *DONE*, but to see the changes on 
[https://people.apache.org/keys/group/sling.asc](https://people.apache.org/keys/group/sling.asc)
 you may need to wait a few hours
 
 1. You also have to add your public key either on `pool.sks-keyservers.net` or 
`pgp.mit.edu` (for the staging repository). To do so you can follow these steps:
@@ -336,7 +338,7 @@ Considering that you are using a \*nix s
 
             $ gpg --list-secret-keys.
         
-       The output is something like this
+        The output is something like this
        
             gpg --list-secret-keys
             /Users/konradwindszus/.gnupg/secring.gpg
@@ -346,7 +348,8 @@ Considering that you are using a \*nix s
            uid                  Konrad Windszus <[email protected]>
            ssb   2048R/226BCE00 2016-01-21
        
-       The key id in this case is `455ECC7C`.
+        The key id in this case is `455ECC7C`.
+       
     1. Send the key towards e.g. `pool.sks-keyservers.net` via
     
             $ gpg --keyserver pool.sks-keyservers.net --send-key <key-id>


Reply via email to