Fix dev URLs FOLIO-1179

CONTRIBUTING.md

@@ -1,4 +1,4 @@
 # Contribution guidelines
 
 Guidelines for Contributing Code:
-[dev.folio.org/community/contrib-code](http://dev.folio.org/community/contrib-code)
+[dev.folio.org/guidelines/contributing](https://dev.folio.org/guidelines/contributing)

README.md

@@ -32,6 +32,6 @@ Stripes is a toolkit for building single-page web applications that FOLIO UI mod
 ## Additional information
 
 See project [STRPCORE](https://issues.folio.org/browse/STRPCORE)
-at the [FOLIO issue tracker](http://dev.folio.org/community/guide-issues).
+at the [FOLIO issue tracker](https://dev.folio.org/guidelines/issue-tracker/).
 
-Other FOLIO Developer documentation is at [dev.folio.org](http://dev.folio.org/)
+Other FOLIO Developer documentation is at [dev.folio.org](https://dev.folio.org/)

doc/release-procedure.md

@@ -17,7 +17,7 @@ NOTE. This document is subject to revision.
 ## Version numbers, branches and tags
 
 The libraries that make up Stripes adhere to [the FOLIO
-version-numbering scheme](http://dev.folio.org/community/contrib-code#version-numbers), which is essentially identical to [Semantic Versioning](http://semver.org/). All releases are tagged in git.
+version-numbering scheme](https://dev.folio.org/guidelines/contributing/#version-numbers), which is essentially identical to [Semantic Versioning](http://semver.org/). All releases are tagged in git.
 
 Each release is tagged with a name beginning with `v` and followed by the version number -- for example, `v2.3.5`.
 
@@ -82,7 +82,7 @@ Update dependant packages when needed to allow CI to pick up the pre-release ver
 
 ## Notes on testing
 
-XXX to be done. See http://dev.folio.org/doc/automation
+XXX to be done. See https://dev.folio.org/guides/automation
 
 ## Publishing to NPM via Jenkins