Updated document ToC navigation link for gh-pages. (#5)

* - Removed the suppression of ToC pages on gh-pages.
- Removed the document ToC to eliminate duplication.

* - Update release to v8.5.2
- Update circleCI to use { .Revision } instead instead of { checksum "package.json" } (recommended by Miguel - mojaloop/documentation#135)
- Restored ToC in documents - do not want to alter the current document content.

* Corrected the internal document ToC navigation for gh-pages.

Author: HenkKodde

documents/platform-operating-guideline.md

@@ -38,65 +38,65 @@ The Business Rules template that is part of this project can be used independent
 
 ## **Table of Contents -- Platform Operating Guideline Template**
 
-[1 - About This Document](#1-About-This-Document)
+[1 - About This Document](#1-about-this-document)
 
-[1.1 - Scheme Services](#1.1-Scheme-Services)
+[1.1 - Scheme Services](#11-scheme-services)
 
-[1.2 - Open API Specification](#1.2-Open-API-Specification)
+[1.2 - Open API Specification](#12-open-api-specification)
 
-[1.3 - Scheme Use Cases](#1.3-Scheme-Use-Cases)
+[1.3 - Scheme Use Cases](#13-scheme-use-cases)
 
-[1.4 - Scheme Supported Identifiers](#1.4-Scheme-Supported-Identifiers)
+[1.4 - Scheme Supported Identifiers](#14-scheme-supported-identifiers)
 
-[2 - The Account Lookup Service](#2-The-Account-Lookup-Service)
+[2 - The Account Lookup Service](#2-the-account-lookup-service)
 
-[2.1 - Description of the Account Lookup Service](#2.1-Description-of-the-Account-Lookup-Service)
+[2.1 - Description of the Account Lookup Service](#21-description-of-the-account-lookup-service)
 
-[2.2 - Party Request](#2.2-Party-Request)
+[2.2 - Party Request](#22-party-request)
 
-[2.3 - Parties Query](#2.3-Parties-Query)
+[2.3 - Parties Query](#23-parties-query)
 
-[2.4 - Parties Query Response](#2.4-Parties-Query-Response)
+[2.4 - Parties Query Response](#24-parties-query-response)
 
-[3 - The Quote Service](#3-The-Quote-Service)
+[3 - The Quote Service](#3-the-quote-service)
 
-[3.1 - Description of the Quote Service](#3.1-Description-of-the-Quote-Service)
+[3.1 - Description of the Quote Service](#31-description-of-the-quote-service)
 
-[3.2 - Quote Request](#3.2-Quote-Request)
+[3.2 - Quote Request](#32-quote-request)
 
-[3.3 - Quote Response](#3.3-Quote-Response)
+[3.3 - Quote Response](#33-quote-response)
 
-[4 - The Transfer Service](#4-The-Transfer-Service)
+[4 - The Transfer Service](#4-the-transfer-service)
 
-[4.1 - Description of the Transfer Service](#4.1-Description-of-the-Transfer-Service)
+[4.1 - Description of the Transfer Service](#41-description-of-the-transfer-service)
 
-[4.2 - Transfer Request](#4.2-Transfer-Request)
+[4.2 - Transfer Request](#42-transfer-request)
 
-[4.3 - Request to Pay](#4.3-Request-to-Pay)
+[4.3 - Request to Pay](#43-request-to-pay)
 
-[5 - The Settlement Service](#5-The-Settlement-Service)
+[5 - The Settlement Service](#5-the-settlement-service)
 
-[5.1 - Transfer Settlement](#5.1-Transfer-Settlement)
+[5.1 - Transfer Settlement](#51-transfer-settlement)
 
-[5.2 - Fee Settlement: Processing Fees](#5.2-Fee-Settlement:-Processing-Fees)
+[5.2 - Fee Settlement: Processing Fees](#52-fee-settlement:-processing-fees)
 
-[5.3 - Fee Settlement: Interchange Fees](#5.3-Fee-Settlement:-Interchange-Fees)
+[5.3 - Fee Settlement: Interchange Fees](#53-fee-settlement:-interchange-fees)
 
-[6 - The Scheme Management Service](#6-The-Scheme-Management-Service)
+[6 - The Scheme Management Service](#6-the-scheme-management-service)
 
-[6.1 - Description of the Scheme Management Service](#6.1-Description-of-the-Scheme-Management-Service)
+[6.1 - Description of the Scheme Management Service](#61-description-of-the-scheme-management-service)
 
-[6.2 - The Registration Process](#6.2-The-Registration-Process)
+[6.2 - The Registration Process](#62-the-registration-process)
 
-[6.3 - DFSP Customer Service](#6.3-DFSP-Customer-Service)
+[6.3 - DFSP Customer Service](#63-dfsp-customer-service)
 
-[6.4 - Scheme System Management](#6.4-Scheme-System-Management)
+[6.4 - Scheme System Management](#64-scheme-system-management)
 
-[7 - The Fraud Management Service](#7-The-Fraud-Management-Service)
+[7 - The Fraud Management Service](#7-the-fraud-management-service)
 
-[8 - Appendix: Scheme Supported Use Cases and System Parameters](#8-Appendix:-Scheme-Supported-Use-Cases-and-System-Parameters)
+[8 - Appendix: Scheme Supported Use Cases and System Parameters](#8-appendix:-scheme-supported-use-cases-and-system-parameters)
 
-[9 - Appendix: Merchant Category Codes](#9-Appendix:-Merchant-Category-Codes)
+[9 - Appendix: Merchant Category Codes](#9-appendix:-merchant-category-codes)
 
 ## 1. About This Document
 
@@ -227,7 +227,7 @@ The Scheme may wish to provide some mechanism for porting a Scheme ID from one D
 
 The following sections describe each service and the obligations and responsibilities of stakeholders. Each service consists of processes: most of the processes are linked to specific API calls specified in the "Open API Specification" section of this document.
 
-## 2.The Account Lookup Service
+## 2. The Account Lookup Service
 
 ### 2.1 Description of the Account Lookup Service 
 
@@ -517,7 +517,7 @@ following sections:_
 
 7. _Real-time Transaction Interception Options_
 
-8. Appendix: Scheme Supported Use Cases and System Parameters
+## 8. Appendix: Scheme Supported Use Cases and System Parameters
 
 _<ul>This is the same table as appears in the Business Rules document, but it has added the systemic codes necessary for the Platform to recognize a transaction as belonging to a given use case or secondary use case. A scheme would only define Secondary Use Cases if it wanted to write rules and/or specify fees that are unique to that Secondary Use Case</ul>_
 

documents/scheme-business-rules.md

@@ -38,37 +38,37 @@ Scheme Business Rules Template
 
 ## **Table of Contents**
 
-[1 - About These Scheme Business Rules](#1.-about-these-scheme-business-rules)
+[1 - About These Scheme Business Rules](#1-about-these-scheme-business-rules)
 
-[2 - Scheme Goals](#2.-scheme-goals)
+[2 - Scheme Goals](#2-scheme-goals)
 
-[3 - Participation in Scheme](#3.-participation-in-scheme)
+[3 - Participation in Scheme](#3-participation-in-scheme)
 
-[4 - Scheme Business Rules](#4.-scheme-business-rules)
+[4 - Scheme Business Rules](#4-scheme-business-rules)
 
-[5 - Responsibilities and Obligations of the Scheme](#5.-responsibilities-and-obligations-of-the-scheme)
+[5 - Responsibilities and Obligations of the Scheme](#5-responsibilities-and-obligations-of-the-scheme)
 
-[6 - Participant Responsibilities and Obligations of Participants](#6.-participant-responsibilities-and-obligations-of-participants)
+[6 - Participant Responsibilities and Obligations of Participants](#6-participant-responsibilities-and-obligations-of-participants)
 
-[7 - Liability - Allocation of Responsibilities](#7.-liability---allocation-of-responsibilities)
+[7 - Liability - Allocation of Responsibilities](#7-liability---allocation-of-responsibilities)
 
-[8 - Security, Risk Management, and Data Confidentiality](#8.-security-risk-management-and-data-confidentiality)
+[8 - Security, Risk Management, and Data Confidentiality](#8-security-risk-management-and-data-confidentiality)
 
-[9 - Scheme Platform and Services](#9.-scheme-platform-and-services)
+[9 - Scheme Platform and Services](#9-scheme-platform-and-services)
 
-[10 - Exception Management](#10.-exception-management)
+[10 - Exception Management](#10-exception-management)
 
-[11 - Appendix: Associated Documents](#11.-appendix:-associated-documents)
+[11 - Appendix: Associated Documents](#11-appendix-associated-documents)
 
-[12 - Appendix: Onboarding and Exit Processes](#12.-appendix:-onboarding-and-exit-processes)
+[12 - Appendix: Onboarding and Exit Processes](#12-appendix-onboarding-and-exit-processes)
 
-[13 - Appendix: Scheme Services](#13.-appendix:-scheme-services)
+[13 - Appendix: Scheme Services](#13-appendix-scheme-services)
 
-[14 - Appendix: Scheme Supported Use Cases](#14.-appendix:-scheme-supported-use-cases)
+[14 - Appendix: Scheme Supported Use Cases](#14-appendix-scheme-supported-use-cases)
 
-[15 - Appendix: Scheme Fee Schedule](#15.-appendix:-scheme-fee-schedule)
+[15 - Appendix: Scheme Fee Schedule](#15-appendix-scheme-fee-schedule)
 
-[16 - Appendix: Risk Management, Security, Privacy, and Service Standards](#16.-appendix:-risk-management-security-privacy-and-service-standards)
+[16 - Appendix: Risk Management, Security, Privacy, and Service Standards](#16-appendix-risk-management-security-privacy-and-service-standards)
 
 ## **A Guide to This Document**
 
@@ -307,7 +307,7 @@ Section Headings and bulleted entries underneath section headings are actual pro
 
 - The Payee Participant must affirm, upon submission of each Transfer Response with a Transaction State "Committed", that the Transfer is being credited to an account that is AML-compliant and is executed in accordance with any account volume limitations, or any other regulation that apply in the territories in which they operate, and that the Payee has been provided all disclosure and has provided all consents necessary to conduct the Transfer in accordance with the Rules and under Applicable Law.
 
- ## 7. Liability - Allocation of Responsibilities
+## 7. Liability - Allocation of Responsibilities
 
 - Each Participant is responsible for errors made by them, and for fraud committed by its employees or contractors, in accordance with Applicable Law.
 

documents/scheme-key-choices.md

@@ -38,35 +38,35 @@ Although this document is written as a contribution to the Mojaloop community, t
 
 ## **Choices Described in this Document**
 
-[1 - Choice: Ownership of Scheme](#1.-choice:-ownership-of-scheme)
+[1 - Choice: Ownership of Scheme](#1-choice-ownership-of-scheme)
 
-[2 - Choice: Participation in the Scheme](#2.-choice:-participation-in-the-scheme)
+[2 - Choice: Participation in the Scheme](#2-choice-participation-in-the-scheme)
 
-[3 - Choice: Relationship of Scheme to Platform](#3.-choice:-relationship-of-scheme-to-platform)
+[3 - Choice: Relationship of Scheme to Platform](#3-choice-relationship-of-scheme-to-platform)
 
-[4 - Choice: Scope of Scheme Rules and Scheme Rules Authority](#4.-choice:-scope-of-scheme-rules-and-scheme-rules-authority)
+[4 - Choice: Scope of Scheme Rules and Scheme Rules Authority](#4-choice-scope-of-scheme-rules-and-scheme-rules-authority)
 
-[5 - Choice: Use Cases](#5.-choice:-use-cases)
+[5 - Choice: Use Cases](#5-choice-use-cases)
 
-[6 - Choice: QR Codes](#6.-choice:-qr-codes)
+[6 - Choice: QR Codes](#6-choice-qr-codes)
 
-[7 - Choice: Payments Addressing](#7.-choice:-payments-addressing)
+[7 - Choice: Payments Addressing](#7-choice-payments-addressing)
 
-[8 - Choice: Interparticipant Settlement](#8.-choice:-interparticipant-settlement)
+[8 - Choice: Interparticipant Settlement](#8-choice-interparticipant-settlement)
 
-[9 - Choice: Tiered Access](#9.-choice:-tiered-access)
+[9 - Choice: Tiered Access](#9-choice-tiered-access)
 
-[10 - Choice: Scheme Fees and End User Pricing](#10.-choice:-scheme-fees-and-end-user-pricing)
+[10 - Choice: Scheme Fees and End User Pricing](#10-choice-scheme-fees-and-end-user-pricing)
 
-[11 - Choice: Brand Management](#11.-choice:-brand-management)
+[11 - Choice: Brand Management](#11-choice-brand-management)
 
-[12 - Choice: Scheme Connections to Other Schemes](#12.-choice:-scheme-connections-to-other-schemes)
+[12 - Choice: Scheme Connections to Other Schemes](#12-choice-scheme-connections-to-other-schemes)
 
-[13 - Choice: Scheme Use by Other FSP's](#13.-choice:-scheme-use-by-other-fsp's)
+[13 - Choice: Scheme Use by Other FSP's](#13-choice-scheme-use-by-other-fsps)
 
-[14 - Choice: Scheme Risk Management Standards](#14.-choice:-scheme-risk-management-standards)
+[14 - Choice: Scheme Risk Management Standards](#14-choice-scheme-risk-management-standards)
 
-[15 - Choice: Exception Management](#15.-choice:-exception-management)
+[15 - Choice: Exception Management](#15-choice-exception-management)
 
 ## 1. Choice: Ownership of Scheme
 
@@ -342,7 +342,7 @@ Mojaloop as a technology is designed to allow system-to-system connectivity. Sch
 
 The relevant L1P principles here are low cost and "openness". The Mojaloop code in particular has the potential to turn cross-border transactions from ones that are governed by complex relationships (as in the case of traditional correspondent banking) into ones which are competed for in an open, interconnected marketplace. Schemes will need to evaluate the merits of this (arguably promoting lower costs) with the risks of dominance by major institutions. Scheme-to-scheme business arrangements may have a beneficial "level the playing field" characteristics. Hybrid relationships are also possible. This is an evolving area of the payment industry, and one where considerable variety of arrangements are both possible and likely.
 
-## 13 Choice: Scheme Use by Other FSP's
+## 13. Choice: Scheme Use by Other FSP's
 
 A successful L1P aligned scheme will be used by many enterprises -- merchants, billers, government agencies, etc. as well as individual people. There will also be a wide range of other FSPs (Financial Services providers) which are not DFSP's: in other words, which do not hold customer transaction accounts. This includes payments services providers: aggregators, merchant services providers, various DFSP processors, etc., all of which may want to connect to and use the scheme.
 

documents/scheme-participation-agreement.md

@@ -30,9 +30,9 @@ The following documents are part of the project:
 
 [1 - Participation Application and Agreement](#1-participation-application-and-agreement)
 
-[1.1 - Applicable Law](#1.1-applicable-law)
+[1.1 - Applicable Law](#11-applicable-law)
 
-[1.2 - Signature Block: Applicant and Scheme](#1.2-signature-block:-applicant-and-scheme)
+[1.2 - Signature Block: Applicant and Scheme](#12-signature-block-applicant-and-scheme)
 
 # 1. Participation Application and Agreement
 

package-lock.json

@@ -1,6 +1,6 @@
 {
   "name": "mojaloop-business-docs",
-  "version": "8.5.2",
+  "version": "8.5.3",
   "description": "Mojaloop Business Documentation GitBook Project",
   "dependencies": {
     "express": "4.17.1",