[ofbiz-framework] branch trunk updated: fixed: spelling correction in a link to pluginsdoc document

[holivier]

This is an automated email from the ASF dual-hosted git repository.

holivier pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/ofbiz-framework.git


The following commit(s) were added to refs/heads/trunk by this push:
     new e6dbed5  fixed: spelling correction in a link to pluginsdoc document
e6dbed5 is described below

commit e6dbed5fd62a9486daf50969b2f82c94c5b6c286
Author: holivier <[hidden email]>
AuthorDate: Sun Nov 15 10:44:31 2020 +0100

    fixed: spelling correction in a link to pluginsdoc document
---
 docs/asciidoc/_include/OFBizDocumentationSystem.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/asciidoc/_include/OFBizDocumentationSystem.adoc b/docs/asciidoc/_include/OFBizDocumentationSystem.adoc
index 652a6cf..b3e2503 100644
--- a/docs/asciidoc/_include/OFBizDocumentationSystem.adoc
+++ b/docs/asciidoc/_include/OFBizDocumentationSystem.adoc
@@ -49,7 +49,7 @@ All main files of each component are included in developer-manual.adoc except fo
 For the main files of the plugin components, there are two ways to read them.
 
 On the one hand, the plugin documentation generation process generates one document per plugin, so that you can see
-the list of documents in the link:../../pluginsdoc/html5[pluginsdoc directory] and thus read each of them;
+the list of documents in the link:../../pluginsdoc[pluginsdoc directory] and thus read each of them;
 
 On the other hand, each plugin master file is included in the plugin chapter of the user manual or developer manual,
 depending on whether the plugin is "technical" or "functional".