Use ./ prefix for same-directory links

Matches the link style convention used elsewhere in the repo, including
the docs/chromeos-wifi-enrollment branch.

Author: llewis1234

tutorials/chromeos-device-identity-certificates.mdx

@@ -5,13 +5,13 @@ html_title: Configure ChromeOS Device Identity Certificates for mTLS | Smallstep
 description: Issue mTLS-capable device identity certificates to ChromeOS devices enrolled in Google Workspace, for use in Wi-Fi, VPN, or internal application authentication.
 ---
 
-Smallstep issues two different kinds of certificate to a ChromeOS device enrolled through [Google Workspace](connect-google-workspace-to-smallstep.mdx): a short-lived **attestation certificate**, issued automatically, and a longer-lived **device identity certificate**, which is what you actually use for mTLS — Wi-Fi (802.1X), VPN, or authenticating to internal applications.
+Smallstep issues two different kinds of certificate to a ChromeOS device enrolled through [Google Workspace](./connect-google-workspace-to-smallstep.mdx): a short-lived **attestation certificate**, issued automatically, and a longer-lived **device identity certificate**, which is what you actually use for mTLS — Wi-Fi (802.1X), VPN, or authenticating to internal applications.
 
-This guide covers issuing that device identity certificate. It's a prerequisite for [ChromeOS Wi-Fi Enrollment](protect-wireless-networks.mdx#chromeos-with-google-workspace-acme-device-attestation) and for any other mTLS use case involving ChromeOS devices.
+This guide covers issuing that device identity certificate. It's a prerequisite for [ChromeOS Wi-Fi Enrollment](./protect-wireless-networks.mdx#chromeos-with-google-workspace-acme-device-attestation) and for any other mTLS use case involving ChromeOS devices.
 
 # Prerequisites
 
-- A completed [Connect Google Workspace to Smallstep](connect-google-workspace-to-smallstep.mdx) integration, with devices syncing into Smallstep
+- A completed [Connect Google Workspace to Smallstep](./connect-google-workspace-to-smallstep.mdx) integration, with devices syncing into Smallstep
 - The Smallstep ChromeOS extension deployed to your target Organizational Unit (covered in that same guide)
 
 # Attestation certificate vs. device identity certificate
@@ -102,4 +102,4 @@ The Smallstep dashboard's device detail page may continue to show "This device d
 
 # Next steps
 
-With a device identity certificate issued, continue to [ChromeOS Wi-Fi Enrollment](protect-wireless-networks.mdx#chromeos-with-google-workspace-acme-device-attestation) to use it for passwordless 802.1X Wi-Fi authentication.
+With a device identity certificate issued, continue to [ChromeOS Wi-Fi Enrollment](./protect-wireless-networks.mdx#chromeos-with-google-workspace-acme-device-attestation) to use it for passwordless 802.1X Wi-Fi authentication.

tutorials/connect-google-workspace-to-smallstep.mdx

@@ -141,5 +141,5 @@ After saving the Google Workspace connection, you will see settings for your int
 Within a few minutes, you should see all of your ChromeOS devices in Smallstep's [Devices](https://smallstep.com/app/?next=/devices/all) tab.
 A full sync is performed every 8 hours, and a partial sync every hour.
 
-With the extension deployed, continue to [Configure ChromeOS Device Identity Certificates](chromeos-device-identity-certificates.mdx) — by default the extension only requests a short-lived attestation certificate, which can't be used for Wi-Fi, VPN, or mTLS.
+With the extension deployed, continue to [Configure ChromeOS Device Identity Certificates](./chromeos-device-identity-certificates.mdx) — by default the extension only requests a short-lived attestation certificate, which can't be used for Wi-Fi, VPN, or mTLS.