update links

Author: jmckenna

en/development/rfc/ms-rfc-58.txt

@@ -4,7 +4,7 @@
 MS RFC 58: Kml Output
 ======================================================================
 
-:Date: 2009/03/01
+:Date: 2009-03-01
 :Authors: Dvaid Kana (david.kana at gmail.com)
 :Authors: Thomas.Bonfort (thomas.bonfort at gmail.com)
 :Authors: Yewondwossen Assefa
@@ -208,9 +208,9 @@ General notes on layers
 - Possible to output vector layers as raster using metadata:  "KML_OUTPUTASRASTER" "true"
 - The user  can use the KML_FOLDER_DSIPLAY layer or map level metedata to choose a setting. Possible values are 'check' (default), 'radioFolder', 'checkOffOnly', 'checkHideChildren'.
 - The user can use metedata KML_DESCRIPTION or KML_INCLUDE_ITEMS to define the description attached to each feature.
-- The user can use metedata KML_ALTITUDEMODE to specify how altitude components in the <coordinates> element are interpreted. Possible values are: absolute, relativeToGround, clampToGround. http://code.google.com/apis/kml/documentation/kmlreference.html#altitudemode
-- The user can use metedata KML_EXTRUDE to specify whether to connect the LinearRing to the ground. http://code.google.com/apis/kml/documentation/kmlreference.html#tessellate
-- The user can use metedata KML_TESSELLATE to specify whether to allow the LinearRing to follow the terrain. http://code.google.com/apis/kml/documentation/kmlreference.html#extrude
+- The user can use metedata KML_ALTITUDEMODE to specify how altitude components in the <coordinates> element are interpreted. Possible values are: absolute, relativeToGround, clampToGround. https://developers.google.com/kml/documentation/kmlreference?csw=1#altitudemode
+- The user can use metedata KML_EXTRUDE to specify whether to connect the LinearRing to the ground. https://developers.google.com/kml/documentation/kmlreference?csw=1#tessellate
+- The user can use metedata KML_TESSELLATE to specify whether to allow the LinearRing to follow the terrain. https://developers.google.com/kml/documentation/kmlreference?csw=1#extrude
 
 
 
@@ -318,8 +318,8 @@ Warning and Error Messages
 Testing
 -------------------------------------------------------------------------------
 
-Development is done in mapserver github (https://github.com/MapServer/MapServer/).
-It was initially in  http://svn.osgeo.org/mapserver/sandbox/davidK/
+Development is done in MapServer GitHub (https://github.com/MapServer/MapServer/).
+It was initially in  https://svn.osgeo.org/mapserver/sandbox/davidK/
 
 
 Documentation
@@ -337,7 +337,7 @@ Comments from Review period
 Voting History
 --------------------------------------------------------------------------------
 
-Adopted 2010/04/08 on the condition that this RFC should be cleaned and upadted with more details.
+Adopted 2010-04-08 on the condition that this RFC should be cleaned and upadted with more details.
 This allows to move the source code from the sand box to trunk
 
 - with +1 from DanielM, SteveL, TamasS, AssefaY, TomK, JeffM

en/development/rfc/ms-rfc-99.txt

@@ -34,7 +34,7 @@ overhead.
   to cut down on the maintenance issues that had arose due to the previous code duplications.
   Already at that time dropping support for GD was discussed, but was finally kept for
   8bit modes only at the cost of a higher worload on the maintainers.
-  At the same time, AGG became a central component inside the mapserver library, and was
+  At the same time, AGG became a central component inside the MapServer library, and was
   used for some rendering tasks not supported by other renderers.
 - In 2012, for the 6.2 release, support for GD became optional and could be disabled at
   compile time.