fix links

Author: taylordowns2000

adaptors/collections.md

@@ -60,17 +60,17 @@ fetch all keys which relate to Mr Benn in 2024).
 The Collections API gives you four functions to read, write and remove data from
 a collection.
 
-- Use [`collections.get()`](adaptors/packages/collections-docs#collections_get)
+- Use [`collections.get()`](/adaptors/packages/collections-docs#collections_get)
   to fetch a single value, or batch-download a range of values.
 - Use
-  [`collections.each()`](adaptors/packages/collections-docs#collections_each) to
+  [`collections.each()`](/adaptors/packages/collections-docs#collections_each) to
   efficiently iterate over a range of items in a collection. Recommended for
   large data sets.
-- Use [`collections.set()`](adaptors/packages/collections-docs#collections_set)
+- Use [`collections.set()`](/adaptors/packages/collections-docs#collections_set)
   to upload one or more values to a collection. `set()` is always an "upsert":
   if a key already exists, it's value will be replaced by the new value
 - Use
-  [`collections.remove()`](adaptors/packages/collections-docs#collections_remove)
+  [`collections.remove()`](/adaptors/packages/collections-docs#collections_remove)
   to remove one or more values.
 
 Detailed usage examples are provided below.

adaptors/dynamics.md

@@ -16,7 +16,7 @@ title: Dynamics Adaptor
 
 See [Microsoft docs](https://learn.microsoft.com/en-us/azure/active-directory/) for the latest on supported authentication methods. When integrating with Dynamics via OpenFn, **Access Token** is supported. See this adaptor's [Configuration docs](/adaptors/packages/dynamics-configuration-schema) for more on the required authentication parameters.
 
-See platform docs on [managing credentials](documentation/manage-projects/manage-credentials) for how to configure a credential in OpenFn. If working locally or if using a Raw JSON credential type, then your configuration will look something like this:
+See platform docs on [managing credentials](/documentation/manage-projects/manage-credentials) for how to configure a credential in OpenFn. If working locally or if using a Raw JSON credential type, then your configuration will look something like this:
 
 ```
 {

adaptors/googlehealthcare.md

@@ -17,7 +17,7 @@ The [Google Cloud Healthcare API](https://cloud.google.com/healthcare-api) is a
 1. See [Google Cloud Healthcare API docs](https://cloud.google.com/healthcare-api/docs/authentication#:~:text=You%20can%20authenticate%20to%20the,CLI%20credentials%20and%20ADC%20credentials.) for the latest on supported authentication methods.
 2. When integrating with Google Cloud Healthcare via OpenFn, there is one primary authentication method that is supported: **Access Token**. See this adaptor's [Configuration docs](/adaptors/packages/googlehealthcare-configuration-schema) for more on the required authentication parameters.
 
-See platform docs on [managing credentials](documentation/manage-projects/manage-credentials) for how to configure a credential in OpenFn. If working locally or if using a Raw JSON credential type, then your configuration will look something like this:
+See platform docs on [managing credentials](/documentation/manage-projects/manage-credentials) for how to configure a credential in OpenFn. If working locally or if using a Raw JSON credential type, then your configuration will look something like this:
 
 ```
 {

adaptors/hubtel.md

@@ -19,7 +19,7 @@ Hubtel supports two primary integration options with OpenFn:
 2. When integrating with Hubtel via OpenFn, authentication via **API Key** is supported.
 3. See this adaptor's [Configuration docs](/adaptors/packages/hubtel-configuration-schema) for more on the required authentication parameters.
 
-See platform docs on [managing credentials](documentation/manage-projects/manage-credentials) for how to configure a credential in OpenFn. If working locally or if using a Raw JSON credential type, then your configuration will look something like this:
+See platform docs on [managing credentials](/documentation/manage-projects/manage-credentials) for how to configure a credential in OpenFn. If working locally or if using a Raw JSON credential type, then your configuration will look something like this:
 
 ```
 {

adaptors/mailchimp.md

@@ -18,7 +18,7 @@ Mailchimp supports two primary integration options:
 
 When integrating with Mailchimp via OpenFn, authentication via **API Key** is supported ([see MC docs](https://mailchimp.com/developer/marketing/docs/fundamentals/#connecting-to-the-api). See this adaptor's [Configuration docs](/adaptors/packages/mailchimp-configuration-schema) for more on the required authentication parameters.
 
-See platform docs on [managing credentials](documentation/manage-projects/manage-credentials) for how to configure a credential in OpenFn. If working locally or if using a Raw JSON credential type, then your configuration will look something like this:
+See platform docs on [managing credentials](/documentation/manage-projects/manage-credentials) for how to configure a credential in OpenFn. If working locally or if using a Raw JSON credential type, then your configuration will look something like this:
 
 ```
 {

adaptors/ocl.md

@@ -18,7 +18,7 @@ This option is suited for scheduled synchronization or workflows requiring regul
 ## Authentication
 When integrating with OCL via OpenFn, you must provide a username and password to generate an authorization token ([see OCL docs](https://docs.openconceptlab.org/en/latest/oclapi/overview.html#authentication-and-authorization)). See this adaptor's [Configuration docs](/adaptors/packages/ocl-configuration-schema) for more on the required authentication parameters.
 
-See platform docs on [managing credentials](documentation/manage-projects/manage-credentials) for how to configure a credential in OpenFn. If working locally or if using a Raw JSON credential type, then your configuration will look something like this:
+See platform docs on [managing credentials](/documentation/manage-projects/manage-credentials) for how to configure a credential in OpenFn. If working locally or if using a Raw JSON credential type, then your configuration will look something like this:
 
 ```
 {

adaptors/odoo.md

@@ -21,7 +21,7 @@ Odoo supports two primary integration options with OpenFn:
 2. When integrating with Odoo via OpenFn, authentication via **User Credentials** is supported.
 3. See this adaptor's [Configuration docs](/adaptors/packages/odoo-configuration-schema) for more on the required authentication parameters.
 
-See platform docs on [managing credentials](documentation/manage-projects/manage-credentials) for how to configure a credential in OpenFn. If working locally or if using a Raw JSON credential type, then your configuration will look something like this:
+See platform docs on [managing credentials](/documentation/manage-projects/manage-credentials) for how to configure a credential in OpenFn. If working locally or if using a Raw JSON credential type, then your configuration will look something like this:
 
 ```
 {

adaptors/openmrs.md

@@ -29,7 +29,7 @@ When integrating with OpenMRS via OpenFn, **Basic Authentication** is supported.
 The `instanceUrl`, `username` an `password` properties are all required to
 access your OpenMRS instance.
 
-See [Managing Credentials](documentation/manage-projects/manage-credentials) to
+See [Managing Credentials](/documentation/manage-projects/manage-credentials) to
 configure a credential in OpenFn.
 
 If working locally or if using a Raw JSON credential type, then your

adaptors/sftp.md

@@ -16,7 +16,7 @@ Using this adaptor, you can read and write files (e.g., `csv`, `xls`, `json` fil
 
 When integrating with a SFTP server via OpenFn, you can provide a `username` and `password` for an authorized user to authenticate. See this adaptor's [Configuration docs](/adaptors/packages/sftp-configuration-schema) for more on the required authentication parameters.
 
-See platform docs on [managing credentials](documentation/manage-projects/manage-credentials) for how to configure a credential in OpenFn. If working locally or if using a Raw JSON credential type, then your configuration will look something like this:
+See platform docs on [managing credentials](/documentation/manage-projects/manage-credentials) for how to configure a credential in OpenFn. If working locally or if using a Raw JSON credential type, then your configuration will look something like this:
 
 ```
 {

docs/jobs/job-writing-guide.md

@@ -925,7 +925,7 @@ In a cron workflow, OpenFn will pass the previous state into the next state - so
 state persists across runs. We can take advantage of that to pick up where we
 left off.
 
-You can use the [`cursor()`](adaptors/packages/common-docs#cursor) operation,
+You can use the [`cursor()`](/adaptors/packages/common-docs#cursor) operation,
 which is built-in to most adaptors, to make cursor management easier.
 
 <details>