Mostly copyright updates

README.md

@@ -1,5 +1,5 @@
 <!---
-   Copyright 2017-2018 Ericsson AB.
+   Copyright 2017-2022 Ericsson AB.
    For a full list of individual contributors, please see the commit history.
 
    Licensed under the Apache License, Version 2.0 (the "License");

eiffel-syntax-and-usage/activity-linking.md

@@ -1,5 +1,5 @@
 <!---
-   Copyright 2021 Ericsson AB.
+   Copyright 2022 Ericsson AB.
    For a full list of individual contributors, please see the commit history.
 
    Licensed under the Apache License, Version 2.0 (the "License");
@@ -25,7 +25,7 @@ A _fully event driven pipeline_ in Eiffel terminology is a pipeline where _all_
 
 A _fully orchestrated pipeline_ is completely controlled by a dedicated pipeline orchestrator, such as Jenkins Pipeline or Argo Workflows, and has no activities _triggered_ by Eiffel events. A fully orchestrated pipeline is probably often initiated by a source change in some SCM system, and that source change is then propagated to the pipeline orchestrator through some non-Eiffel-event channel (e.g. an Github web hook or a Gerrit stream-event)
 
-None of the scenarios above is probably relevant for most of the Eiffel event users, but rather a combination of the two where a pipeline is often _triggered_ by an Eiffel event, but then the orchestrator deals with controlling (at least parts of) the pipeline. Such triggers could for example be SCM events ([SCC](../../eiffel-vocabulary/EiffelSourceChangeCreatedEvent.md)/[SCS](../../eiffel-vocabulary/EiffelSourceChangeSubmittedEvent.md)) or artifact events ([ArtC](../../eiffel-vocabulary/EiffelArtifactCreatedEvent.md)/[ArtP](../../eiffel-vocabulary/EiffelArtifactOublishedEvent.md)/[CLM](../../eiffel-vocabulary/EiffelConfidenceLevelModifiedEvent.md)).
+None of the scenarios above is probably relevant for most of the Eiffel event users, but rather a combination of the two where a pipeline is often _triggered_ by an Eiffel event, but then the orchestrator deals with controlling (at least parts of) the pipeline. Such triggers could for example be SCM events ([SCC](../eiffel-vocabulary/EiffelSourceChangeCreatedEvent.md)/[SCS](../eiffel-vocabulary/EiffelSourceChangeSubmittedEvent.md)) or artifact events ([ArtC](../eiffel-vocabulary/EiffelArtifactCreatedEvent.md)/[ArtP](../eiffel-vocabulary/EiffelArtifactPublishedEvent.md)/[CLM](../eiffel-vocabulary/EiffelConfidenceLevelModifiedEvent.md)).
 
 ## Link Types Involved
 This section describes the main link types involved in linking activities in pipelines
@@ -39,7 +39,7 @@ __Legal targets:__ Any
 __Multiple allowed:__ Yes  
 
 ### PRECURSOR
-This link type is used to declare *temporal relationships* between [activities](https://github.com/eiffel-community/eiffel/blob/master/eiffel-syntax-and-usage/glossary.md#activity) in a [pipeline](https://github.com/eiffel-community/eiffel/blob/master/eiffel-syntax-and-usage/glossary.md#pipeline), i.e. what other activity preceded this activity.
+This link type is used to declare *temporal relationships* between [activities](../eiffel-syntax-and-usage/glossary.md#activity) in a [pipeline](../eiffel-syntax-and-usage/glossary.md#pipeline), i.e. what other activity preceded this activity.
 
 ![alt text](./precursor-simple.png "Simple PRECURSOR Example")
 
@@ -63,7 +63,7 @@ __Legal targets:__ [EiffelActivityTriggeredEvent](../eiffel-vocabulary/EiffelAct
 __Multiple allowed:__ Yes  
 
 ### CONTEXT
-This link type is used to declare *hierarchies* of [activities](https://github.com/eiffel-community/eiffel/blob/master/eiffel-syntax-and-usage/glossary.md#activity) within a [pipeline](https://github.com/eiffel-community/eiffel/blob/master/eiffel-syntax-and-usage/glossary.md#pipeline).
+This link type is used to declare *hierarchies* of [activities](../eiffel-syntax-and-usage/glossary.md#activity) within a [pipeline](../eiffel-syntax-and-usage/glossary.md#pipeline).
 The CONTEXT identifies the activity or test suite of which this event constitutes a part.
 Examples:
 - This *pipeline step* is executed in the *CONTEXT* of that *pipeline*, i.e. the pipeline step is part of a certain pipeline
@@ -76,7 +76,7 @@ __Legal targets:__ [EiffelActivityTriggeredEvent](../eiffel-vocabulary/EiffelAct
 __Multiple allowed:__ Yes  
 
 ### FLOW_CONTEXT
-Identifies the flow context of the event: which is the continuous integration and delivery flow in which this occurred – e.g. which product, project, track or version this is applicable to.
+Identifies the [flow](../eiffel-syntax-and-usage/glossary.md#flow) context of the event: which is the continuous integration and delivery flow in which this occurred – e.g. which product, project, track or version this is applicable to.
 
 __Required:__ No  
 __Legal sources:__ Any  

eiffel-syntax-and-usage/glossary.md

@@ -143,7 +143,7 @@ The terms below are not used in any events in the Eiffel protocol. They are adde
 
 ### Occurrence
 
-An _occurrence_ is the capture of a statement of fact during the execution of a CI/CD [pipeline](#pipeline). This might occur because of for example a source change being created/updated, an artifact being built, an upstream artifact being delivered, or any other activity relevant to a CI/CD pipeline.
+An _occurrence_ is the capture of a statement of fact during the execution of a CI/CD [pipeline](#pipeline). This might occur because of a source change being created/updated, an artifact being built, an upstream artifact being delivered, or any other activity relevant to a CI/CD pipeline.
 
 ### Pipeline
 

usage-examples/activity-linking/README.md

@@ -1,3 +1,20 @@
+<!---
+   Copyright 2022 Ericsson AB.
+   For a full list of individual contributors, please see the commit history.
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.
+--->
+
 # Activity Linking
 
 This section of the usage examples focus on different ways to link activity related events in different scenarios

usage-examples/activity-linking/combined-pipeline.md

@@ -1,5 +1,5 @@
 <!---
-   Copyright 2021 Ericsson AB.
+   Copyright 2022 Ericsson AB.
    For a full list of individual contributors, please see the commit history.
 
    Licensed under the Apache License, Version 2.0 (the "License");

usage-examples/activity-linking/event-driven-pipeline.md

@@ -1,5 +1,5 @@
 <!---
-   Copyright 2021 Ericsson AB.
+   Copyright 2022 Ericsson AB.
    For a full list of individual contributors, please see the commit history.
 
    Licensed under the Apache License, Version 2.0 (the "License");

usage-examples/activity-linking/network-of-pipelines.md

@@ -1,5 +1,5 @@
 <!---
-   Copyright 2021 Ericsson AB.
+   Copyright 2022 Ericsson AB.
    For a full list of individual contributors, please see the commit history.
 
    Licensed under the Apache License, Version 2.0 (the "License");

usage-examples/activity-linking/orchestrated-pipeline.md

@@ -1,5 +1,5 @@
 <!---
-   Copyright 2021 Ericsson AB.
+   Copyright 2022 Ericsson AB.
    For a full list of individual contributors, please see the commit history.
 
    Licensed under the Apache License, Version 2.0 (the "License");