Add links for RFCs

1 files changed, 2 insertions, 2 deletions

diff --git a/bip-http-address-service.mediawiki b/bip-http-address-service.mediawiki
index 52df7ba..ac00e08 100644
--- a/bip-http-address-service.mediawiki
+++ b/bip-http-address-service.mediawiki
@@ -46,11 +46,11 @@ This flow will use a HTTP OPTIONS request to the address endpoint URL in order t
  
 ====Allow Header Usage====
 
-The '''Allow''' header is used, as defined in [https://tools.ietf.org/html/rfc2616 RFC2616 RFC 2616] (14.7), to supply the client with supported HTTP methods for use with the address endpoint URL. The '''Allow''' header must return supported HTTP methods for the available return MIME types. See the table below for HTTP methods that relate to supported return MIME types.
+The '''Allow''' header is used, as defined in [https://tools.ietf.org/html/rfc2616 RFC 2616] (14.7), to supply the client with supported HTTP methods for use with the address endpoint URL. The '''Allow''' header must return supported HTTP methods for the available return MIME types. See the table below for HTTP methods that relate to supported return MIME types.
 
 ====Accept Header Usage====
 
-The '''Accept''' header is defined in [[https://tools.ietf.org/html/rfc2616 RFC 2616] (14.1) and is used in the OPTIONS response. This header is generally used in the client request, but this specification uses it in the Address Service OPTIONS response.
+The '''Accept''' header is defined in [https://tools.ietf.org/html/rfc2616 RFC 2616] (14.1) and is used in the OPTIONS response. This header is generally used in the client request, but this specification uses it in the Address Service OPTIONS response.
 
 The '''Accept''' header MUST contain all acceptable MIME types for the endpoint. The following table defines MIME types for the appropriate return values: