Merge branch 'master' into ongoing-release-versions

README.md

@@ -80,6 +80,8 @@ The master branch is automatically deployed as [dev.folio.org](https://dev.folio
 
 Other branches are re-built upon push of changes. Follow the GitHub link from the branch's continuous-integration details to view the generated branch site.
 
+**NOTE:** Since May 2023 the AWS Codebuild system has denied building of new branches via the GitHub UI. A new branch can still be created, and used locally, and used for the pull-request. But the ability to view an AWS build of the branch via GitHub is now gone.
+
 ## Additional information
 
 Refer to FAQs regarding [Developer documentation](https://dev.folio.org/faqs/#developer-documentation) and [Raising Jira tickets](https://dev.folio.org/faqs/how-to-contribute-devdoc/#raising-jira-tickets).

_data/config-apidocs.json

@@ -1984,7 +1984,7 @@
       "apiTypes": [
         "RAML"
       ],
-      "generator": "api_doc.py 1.5.4"
+      "generator": "api_doc.py 1.5"
     },
     "name": "okapi",
     "org": "folio-org"

_faqs/how-to-contribute-devdoc.md

@@ -32,7 +32,7 @@ The set of FAQs are located in the `_faqs` directory, as [explained](/faqs/how-t
 
 ## Creating new docs
 
-Follow the FAQs for new [/faqs/#developer-documentation](/faqs/#developer-documentation).
+Follow the FAQs section for new [Developer documentation](/faqs/#developer-documentation).
 
 ## Raising Jira tickets