Auto-deploy docs built from commit c1fdfc0

COVESA · Jan 24, 2024 · 4019489 · 4019489
1 parent 346a10f
commit 4019489
Show file tree

Hide file tree

Showing 6 changed files with 7 additions and 7 deletions.
diff --git a/developers-manual.md b/developers-manual.md
@@ -6,7 +6,7 @@
 
 ## Table of Contents
 
-Documentation generated from: 605c32fb90d9106261b1289a0dcd946ec9a5e899
+Documentation generated from: c1fdfc022492990f3a5356eec1f8f91d1a58656f
 
 - [Mapping documents](#mapping-documents)  
 - [Datatype mapping](#datatype-mapping)  

diff --git a/generated-developers-toc.md b/generated-developers-toc.md
@@ -1,4 +1,4 @@
-Documentation generated from: 605c32fb90d9106261b1289a0dcd946ec9a5e899
+Documentation generated from: c1fdfc022492990f3a5356eec1f8f91d1a58656f
 
 - [Mapping documents](#mapping-documents)  
 - [Datatype mapping](#datatype-mapping)  

diff --git a/generated-specification.stage1.md b/generated-specification.stage1.md
@@ -206,7 +206,7 @@ that have a name, a datatype, a unit and meaning but the transfer of data is
 defined by separate protocols built on top of VSS.  In other words, VSS
 typically uses the the second interpretation, and VSS Signals can then be
 represented by Properties in IFEX.  (Refer to the [separate
-analysis](static-vss_integration_proposal.md) of the IFEX/VSS relationship).
+analysis](static-vss_integration_proposal) of the IFEX/VSS relationship).
 
 --------------------
 

diff --git a/generated-toc.md b/generated-toc.md
@@ -1,4 +1,4 @@
-Documentation generated from: 605c32fb90d9106261b1289a0dcd946ec9a5e899
+Documentation generated from: c1fdfc022492990f3a5356eec1f8f91d1a58656f
 
 - [FEATURES](#features)  
     - [Features that are not included _in the core IDL_, but worth describing](#features-that-are-not-included-in-the-core-idl-but-worth-describing)  

diff --git a/ifex-specification.md b/ifex-specification.md
@@ -13,7 +13,7 @@ License: Creative Commons Attribution 4.0 International
 License (CC-BY-4.0), described [here](https://creativecommons.org/licenses/by/4.0/)
 
 <!-- Heading and TOC -->
-Documentation generated from: 605c32fb90d9106261b1289a0dcd946ec9a5e899
+Documentation generated from: c1fdfc022492990f3a5356eec1f8f91d1a58656f
 
 - [FEATURES](#features)  
     - [Features that are not included _in the core IDL_, but worth describing](#features-that-are-not-included-in-the-core-idl-but-worth-describing)  
@@ -287,7 +287,7 @@ that have a name, a datatype, a unit and meaning but the transfer of data is
 defined by separate protocols built on top of VSS.  In other words, VSS
 typically uses the the second interpretation, and VSS Signals can then be
 represented by Properties in IFEX.  (Refer to the [separate
-analysis](static-vss_integration_proposal.md) of the IFEX/VSS relationship).
+analysis](static-vss_integration_proposal) of the IFEX/VSS relationship).
 
 --------------------
 

diff --git a/static-general-description.md b/static-general-description.md
@@ -205,7 +205,7 @@ that have a name, a datatype, a unit and meaning but the transfer of data is
 defined by separate protocols built on top of VSS.  In other words, VSS
 typically uses the the second interpretation, and VSS Signals can then be
 represented by Properties in IFEX.  (Refer to the [separate
-analysis](static-vss_integration_proposal.md) of the IFEX/VSS relationship).
+analysis](static-vss_integration_proposal) of the IFEX/VSS relationship).
 
 --------------------