small change

diff --git a/best_practices.mdwn b/best_practices.mdwn
index 861b2a411424019e3f30acb85991b03c2155ffbe..f3c2df54c6a4f32bdcf2ffc51b974107f878df38 100644 (file)
--- a/best_practices.mdwn
+++ b/best_practices.mdwn
@@ -2,9 +2,6 @@
 
 Translations: [[Castellano|best practices_es]]
 
-Spanish version: https://pad.puscii.nl/p/Practice-es
-Portuguese version: https://pad.puscii.nl/p/Practice-pt
-
 *This appendix contains the text of the policy with specific best practices added below relevant sections. It is a work in progress. Please help expand!*
 
 Obviously, every security/privacy level requires that you keep your software up to date to the current knowledge of security issues.
@@ -15,14 +12,14 @@ Obviously, every security/privacy level requires that you keep your software up
 
 #### Level 1
 
-##### [StartTLS-exim](http://aland.burngreave.net/archives/2009/12/30/index.html#e2009-12-30T16_26_49.txt) starttls with other compliant servers’, certs verified against cacert/…
-
 ### If the server adds the IP address of a user sending a mail through its service anywhere in the email, the user is informed about this.
 
 ### The connections between the user and the server are always encrypted.
 
 ### Use StartTLS to exchange mails with other servers whenever available.
 
+[StartTLS-exim](http://aland.burngreave.net/archives/2009/12/30/index.html#e2009-12-30T16_26_49.txt) starttls with other compliant servers’, certs verified against cacert/…
+
 ### The server must have its own SSL certificate signed by one of a  given  set of certificate authorities. See best practices documents for   details.
 
 #### Level 2