update

unibz-core · Jul 9, 2024 · 82c7a86 · 82c7a86
1 parent 1623eba
commit 82c7a86
Show file tree

Hide file tree

Showing 10 changed files with 6 additions and 6 deletions.
diff --git a/docs/Terminology.md b/docs/Terminology.md
@@ -45,7 +45,7 @@ In ArchiMate, a *Control Capability* is represented by a *Capability* associated
 
 A *Security Mechanism* aggregates *Control Capabilities*. However, other objects may also have one or more *Control Capabilities*.
 
-**Examples:** Antivirus software has *Control Capabilities* to scan and eliminate malwares. Air defense systems have *Control Capabilities* to intercept certain air threats. Warning signs have *Control Capabilities* to dissuade people from doing certain things.
+**Examples:** Antivirus software has *Control Capabilities* to scan and eliminate malware. Air defense systems have *Control Capabilities* to intercept certain air threats. Warning signs have *Control Capabilities* to dissuade people from doing certain things.
 
 
 
@@ -117,11 +117,11 @@ In ArchiMate, an *Intention* is represented by a *Goal*.
 <!-- TOC --><a name="likelihood"></a>
 ### 8. Likelihood
 
-> Definition...
+> A likelihood assignment describes the chances of occurrence of certain types of events or the chances of events to cause (or be followed by) other events.
 
-In ArchiMate, Likelihood is represented by an *Assessment* with the stereotype «Likelihood»...
+In ArchiMate, *Likelihood* is represented by an *Assessment* with the stereotype «Likelihood», which can be connected to an event or the triggering association between events. Since there is no sense in assigning likelihood to individual events, the likelihood assignment should be understood as describing regularities, so applicable to types of events.
 
-connected to a triggering association between Value Events or to a «ValueExperience»
+Events that prevent others from happening can be understood as negatively influencing the likelihood of the occurrence of the latter.
 
 **Examples:** XXXX.
 

diff --git a/docs/_config.yml b/docs/_config.yml
@@ -8,12 +8,12 @@ url: https://just-the-docs.github.io
 color_scheme: light
 
 # Set a path/url to a logo that will be displayed instead of the title
-logo: "sec3.png"
+logo: "assets/sec3.png"
 
 # Set a path/url to a favicon that will be displayed by the browser
 # favicon_ico: "/assets/images/favicon.ico"
 # If the path to your favicon is /favicon.ico, you can leave favicon_ico unset.
-favicon_ico: "sec.ico"
+favicon_ico: "assets/sec.ico"
 
 aux_links:
   Repository: https://github.com/unibz-core/security-archimate

diff --git a/docs/doc.png → docs/assets/doc.png b/docs/doc.png → docs/assets/doc.png
diff --git a/docs/favicon.ico → docs/assets/favicon.ico b/docs/favicon.ico → docs/assets/favicon.ico
diff --git a/docs/just-the-docs.png → docs/assets/just-the-docs.png b/docs/just-the-docs.png → docs/assets/just-the-docs.png
diff --git a/docs/publications.md → docs/assets/publications.md b/docs/publications.md → docs/assets/publications.md
diff --git a/docs/sec.ico → docs/assets/sec.ico b/docs/sec.ico → docs/assets/sec.ico
diff --git a/docs/sec.png → docs/assets/sec.png b/docs/sec.png → docs/assets/sec.png
diff --git a/docs/sec2.png → docs/assets/sec2.png b/docs/sec2.png → docs/assets/sec2.png
diff --git a/docs/sec3.png → docs/assets/sec3.png b/docs/sec3.png → docs/assets/sec3.png