feat: change artifact to artefact across the spec

Signed-off-by: Pavel Shukhman <[email protected]>

Author: taleodor

api-flow/publisher.md

@@ -19,7 +19,7 @@ sequenceDiagram
     Vendor ->> tea_component: POST to /v1/component with the TEA PI and component version as the payload
     tea_component ->> Vendor: Component is created and a TEA Component ID is returned
 
-    Vendor ->> tea_collection: POST to /v1/collection with the TEA Component ID as the and the artifact as payload
+    Vendor ->> tea_collection: POST to /v1/collection with the TEA Component ID as the and the artefact as payload
     tea_collection ->> Vendor: Collection is created with the collection ID returned
 
 ```
@@ -39,13 +39,13 @@ sequenceDiagram
     Vendor ->> tea_component: POST to /v1/component with the TEA PI and component version as the payload
     tea_component ->> Vendor: Component is created and a TEA Component ID is returned
 
-    Note over Vendor,TEA Component: Add an artifact (e.g. SBOM)
-    Vendor ->> tea_collection: POST to /v1/collection with the TEA Component ID as the and the artifact as payload
+    Note over Vendor,TEA Component: Add an artefact (e.g. SBOM)
+    Vendor ->> tea_collection: POST to /v1/collection with the TEA Component ID as the and the artefact as payload
     tea_collection ->> Vendor: Collection is created with the collection ID returned
 
 ```
 
-## Adding a new artifact
+## Adding a new artefact
 
 ```mermaid
 sequenceDiagram
@@ -58,6 +58,6 @@ sequenceDiagram
     Vendor ->> tea_component: GET to /v1/component with the TEA PI to get the latest version
     tea_component ->> Vendor: Component will be returned
 
-    Vendor ->> tea_collection: POST to /v1/collection with the TEA Component ID as the and the artifact as payload
+    Vendor ->> tea_collection: POST to /v1/collection with the TEA Component ID as the and the artefact as payload
     tea_collection ->> Vendor: Collection is created with the collection ID returned
 ```

archive/README.md

@@ -0,0 +1 @@
+This directory contains archived versions of the API specification and related documentation. These files are preserved for historical reference and should not be used for current development.