docs: fix typos: PCFs without apostroph

Author: schuur

decisions/log/0041-version-simplification.md

@@ -46,7 +46,7 @@ Starting PACT 4.x the properties `version` and `updated` will be made obsolete.
 Any 3.x implementation of the PACT API does not need to implement any reasoning to distinguish between major and minor changes. 
 
 ### Backwards and forwards compatibility
-Changes originating in 3.x will be handled correctly by 2.x API's: any change involve a new ID and a link back to the old ID. So, in terms of 2.x, the change is a *major* one, which will deprecate previous PCF's. 
+Changes originating in 3.x will be handled correctly by 2.x API's: any change involve a new ID and a link back to the old ID. So, in terms of 2.x, the change is a *major* one, which will deprecate previous PCFs. 
 The one exception of a change originating in 3.x is the deprecation of an old PCF *without* it being replaced by a new one. In this case the ID will not change, but the status does (and be set to `Deprecated`).
 
 Major changes originating in 2.x will be be handled correctly by 3.x API's. 

decisions/log/0042-add-filter-to-async-api.md

@@ -73,9 +73,9 @@ As a consequence, after consulting with the Tech WG on 15/1/2025 a limited list
 * `companyId` (string) can be 1 or more company ID's. Will return all footprints with corresponding id's in the `companyIds` attribute. Note that a footprint itself can also have multiple company IDs.
 * `geography` (string) can be 1 or more geographic specifiers. Values specified can denote `geographicRegion` or `geographyCountry` or `geographyCountrySubdivision`. Will return all footprints within the specified geography.
 * `classification` (string) can be 1 or more product classifications. Will return all footprints with corresponding values in the `productClassifications` attribute. Note that a footprint itself can have multiple classifications.
-* `validOn` (date-string) will match all PCF's which where valid on the date specified: footprint.validityPeriodBegin <= validOn AND validFrom <= footprint.validityPeriodEnd
-* `validAfter` (date-string) will match PCF's whith validAfter < footprint.validityPeriodBegin
-* `validBefore` (date-string) will match PCF's whith validBefore > footprint.validityPeriodEnd
+* `validOn` (date-string) will match all PCFs which where valid on the date specified: footprint.validityPeriodBegin <= validOn AND validFrom <= footprint.validityPeriodEnd
+* `validAfter` (date-string) will match PCFs whith validAfter < footprint.validityPeriodBegin
+* `validBefore` (date-string) will match PCFs whith validBefore > footprint.validityPeriodEnd
 * `status` (string) Can be "Active" or "Deprecated"
 * **MAYBE?**`pfId` (string) Search for a specific Product Footprint Id. Note that this is synonymous with calling `/footprints/{pfid}`
 

spec/v3/index.md

@@ -175,7 +175,7 @@ This chapter provides examples for inter-company business cases related to the e
 
 ## Asynchronous Exchange ## {#business-cases-async-events}
 
-Exchanging PCF's asynchronously requires **both** the [=data owner=] **and** the [=data recipient=] to run a PACT conformant host system, **both** sides being able to initiate communication to each other.
+Exchanging PCFs asynchronously requires **both** the [=data owner=] **and** the [=data recipient=] to run a PACT conformant host system, **both** sides being able to initiate communication to each other.
 
 
 ### Requesting a PCF
@@ -204,16 +204,16 @@ Refer to [[#api-action-events]] for detailed request and response formats.
 
 ## Synchronous retrieval 
 
-The synchronous part of te API allows for immediate retrieval of PCF's. Refer to [[#api-action-list]] and [[#api-action-get]] for detailed request and response formats.
+The synchronous part of te API allows for immediate retrieval of PCFs. Refer to [[#api-action-list]] and [[#api-action-get]] for detailed request and response formats.
 
 
-### Getting multiple PCF's
+### Getting multiple PCFs
 
-The `ListFootprints` action allows for directly retrieving multiple PCF's. Starting from version 3.0, host systems
+The `ListFootprints` action allows for directly retrieving multiple PCFs. Starting from version 3.0, host systems
 must provide filtering on a minimum set of criteria. 
 
 1. The data recipient authenticates with the data owner.
-2. The data recipient calls the `/footprints` endpoint, optionally providing a filter with search criteria and a limit to obtain a list of PCF's. 
+2. The data recipient calls the `/footprints` endpoint, optionally providing a filter with search criteria and a limit to obtain a list of PCFs. 
 3. After validating the request, the data owner returns a 2xx status code and the list of {<ProductFootprint>} objects. On error the data owner returns a relevant HTTP error code. For details, see [#rest-api]
 
 

spec/v3/openapi.yaml

@@ -902,7 +902,7 @@ components:
           description: |
             If present, a description of any allocation rules applied and the rationale explaining how the selected approach aligns with [=PACT Methodology=] rules (see Section 3.3.1.4).
           summary: |
-            Description of the allocation rules applied to the PCF's foreground data 
+            Description of the allocation rules applied to the PCFs foreground data 
             including an explanation of the underlying reasons (way of allocating 
             all activities from your manufacturing steps to the declared unit).
           type: string
@@ -1521,23 +1521,23 @@ components:
     validOn:
       name: validOn
       description: |
-        If present, MUST match all PCF's which where valid on the date specified: footprint.validityPeriodBegin <= validOn AND validFrom <= footprint.validityPeriodEnd
+        If present, MUST match all PCFs which where valid on the date specified: footprint.validityPeriodBegin <= validOn AND validFrom <= footprint.validityPeriodEnd
       in: query
       schema:
         type: string
         format: date-time
     validAfter:
       name: validAfter
       description: |
-        if present, MUST match PCF's whith validAfter < footprint.validityPeriodBegin
+        if present, MUST match PCFs whith validAfter < footprint.validityPeriodBegin
       in: query
       schema:
         type: string
         format: date-time
     validBefore:
       name: validBefore
       description: |
-        if present, MUST match PCF's whith validBefore > footprint.validityPeriodEnd
+        if present, MUST match PCFs whith validBefore > footprint.validityPeriodEnd
       in: query
       schema:
         type: string

spec/v3/rest-api.md

@@ -236,11 +236,11 @@ Note: Optional filtering specified in version 2.2+ (based on OData4) is NOW DEPR
 : `classification` array(string) 
 :: if present, MUST be 1 or more product classifications. Will return all footprints with corresponding values in the `productClassifications` attribute. Note that a footprint itself can have multiple classifications.
 : `validOn` (date-string) 
-:: if present, MUST match all PCF's which where valid on the date specified: footprint.validityPeriodBegin <= validOn AND validFrom <= footprint.validityPeriodEnd
+:: if present, MUST match all PCFs which where valid on the date specified: footprint.validityPeriodBegin <= validOn AND validFrom <= footprint.validityPeriodEnd
 : `validAfter` (date-string) 
-:: if present, MUST match PCF's whith validAfter < footprint.validityPeriodBegin
+:: if present, MUST match PCFs whith validAfter < footprint.validityPeriodBegin
 : `validBefore` (date-string) 
-:: if present, MUST match PCF's whith validBefore > footprint.validityPeriodEnd
+:: if present, MUST match PCFs whith validBefore > footprint.validityPeriodEnd
 : `status` (string) 
 :: If Present, MUST be either be "Active" or "Deprecated"
 
@@ -577,11 +577,11 @@ with
 : `classification` array(string) 
 :: if present, MUST be 1 or more product classifications. Will return all footprints with corresponding values in the `productClassifications` attribute. Note that a footprint itself can have multiple classifications.
 : `validOn` (date-string) 
-:: if present, MUST match all PCF's which where valid on the date specified: footprint.validityPeriodBegin <= validOn AND validFrom <= footprint.validityPeriodEnd
+:: if present, MUST match all PCFs which where valid on the date specified: footprint.validityPeriodBegin <= validOn AND validFrom <= footprint.validityPeriodEnd
 : `validAfter` (date-string) 
-:: if present, MUST match PCF's whith validAfter < footprint.validityPeriodBegin
+:: if present, MUST match PCFs whith validAfter < footprint.validityPeriodBegin
 : `validBefore` (date-string) 
-:: if present, MUST match PCF's whith validBefore > footprint.validityPeriodEnd
+:: if present, MUST match PCFs whith validBefore > footprint.validityPeriodEnd
 : `status` (string) 
 :: If Present, MUST be either be "Active" or "Deprecated"
 : <dfn>PFRequestComment</dfn>