URLs changed from abs path to relative path

6 files changed, 7 insertions, 7 deletions

diff --git a/contributors/design-proposals/api-machinery/customresource-conversion-webhook.md b/contributors/design-proposals/api-machinery/customresource-conversion-webhook.md
index 453884e4..54991fd6 100644
--- a/contributors/design-proposals/api-machinery/customresource-conversion-webhook.md
+++ b/contributors/design-proposals/api-machinery/customresource-conversion-webhook.md
@@ -148,7 +148,7 @@ in *CRD v1* (apiextensions.k8s.io/v1), there will be only version list with no t
 
 #### Alternative approaches considered
 
-First a defaulting approach is considered which per-version fields would be defaulted to top level fields. but that breaks backward incompatible change; Quoting from API [guidelines](https://git.k8s.io/community/contributors/devel/sig-architecture/api_changes.md#backward-compatibility-gotchas):
+First a defaulting approach is considered which per-version fields would be defaulted to top level fields. but that breaks backward incompatible change; Quoting from API [guidelines](/contributors/devel/sig-architecture/api_changes.md#backward-compatibility-gotchas):
 
 > A single feature/property cannot be represented using multiple spec fields in the same API version simultaneously
 
diff --git a/contributors/design-proposals/cluster-lifecycle/runtimeconfig.md b/contributors/design-proposals/cluster-lifecycle/runtimeconfig.md
index ff6335a1..c1f30f5c 100644
--- a/contributors/design-proposals/cluster-lifecycle/runtimeconfig.md
+++ b/contributors/design-proposals/cluster-lifecycle/runtimeconfig.md
@@ -47,7 +47,7 @@ feature's owner(s). The following are suggested conventions:
 - Features that touch multiple components should reserve the same key
   in each component to toggle on/off.
 - Alpha features should be disabled by default. Beta features may
-  be enabled by default. Refer to [this file](https://git.k8s.io/community/contributors/devel/sig-architecture/api_changes.md#alpha-beta-and-stable-versions)
+  be enabled by default. Refer to [this file](/contributors/devel/sig-architecture/api_changes.md#alpha-beta-and-stable-versions)
   for more detailed guidance on alpha vs. beta.
 
 ## Upgrade support
diff --git a/contributors/design-proposals/network/external-lb-source-ip-preservation.md b/contributors/design-proposals/network/external-lb-source-ip-preservation.md
index 11359e1a..f6a7d680 100644
--- a/contributors/design-proposals/network/external-lb-source-ip-preservation.md
+++ b/contributors/design-proposals/network/external-lb-source-ip-preservation.md
@@ -50,7 +50,7 @@ lot of applications and customer use-cases.
 # Alpha Design
 
 This section describes the proposed design for
-[alpha-level](https://git.k8s.io/community/contributors/devel/sig-architecture/api_changes.md#alpha-beta-and-stable-versions) support, although
+[alpha-level](/contributors/devel/sig-architecture/api_changes.md#alpha-beta-and-stable-versions) support, although
 additional features are described in [future work](#future-work).
 
 ## Overview
diff --git a/contributors/design-proposals/node/secret-configmap-downwardapi-file-mode.md b/contributors/design-proposals/node/secret-configmap-downwardapi-file-mode.md
index 2a492b38..1d5bd7b7 100644
--- a/contributors/design-proposals/node/secret-configmap-downwardapi-file-mode.md
+++ b/contributors/design-proposals/node/secret-configmap-downwardapi-file-mode.md
@@ -49,7 +49,7 @@ This was asked on the mailing list here[2] and here[3], too.
 Several alternatives have been considered:
 
  * Add a mode to the API definition when using secrets: this is backward
-   compatible as described [here](https://git.k8s.io/community/contributors/devel/sig-architecture/api_changes.md) IIUC and seems like the
+   compatible as described [here](/contributors/devel/sig-architecture/api_changes.md) IIUC and seems like the
    way to go. Also @thockin said in the ML that he would consider such an
    approach. But it might be worth to consider if we want to do the same for
    configmaps or owners, but there is no need to do it now either.
diff --git a/contributors/guide/coding-conventions.md b/contributors/guide/coding-conventions.md
index 25abdd6f..87e6432f 100644
--- a/contributors/guide/coding-conventions.md
+++ b/contributors/guide/coding-conventions.md
@@ -55,7 +55,7 @@ the name of the directory in which the .go file exists.
 sync.Mutex`). When multiple locks are present, give each lock a distinct name
 following Go conventions - `stateLock`, `mapLock` etc.
 
-    - [API changes](https://git.k8s.io/community/contributors/devel/sig-architecture/api_changes.md)
+    - [API changes](/contributors/devel/sig-architecture/api_changes.md)
 
     - [API conventions](/contributors/devel/api-conventions.md)
 
diff --git a/sig-architecture/api-review-process.md b/sig-architecture/api-review-process.md
index f085837b..5a675caa 100644
--- a/sig-architecture/api-review-process.md
+++ b/sig-architecture/api-review-process.md
@@ -227,9 +227,9 @@ Aspiring reviewers should reach out the moderator on slack.  The moderator will
 
 * [Updating-docs-for-feature-changes.md](https://git.k8s.io/sig-release/release-team/role-handbooks/documentation-guides/updating-docs-for-feature-changes.md#when-making-api-changes)
 
-* [https://git.k8s.io/community/contributors/devel/sig-architecture/api_changes.md](/contributors/devel/sig-architecture/api_changes.md)
+* [Api_changes.md](/contributors/devel/sig-architecture/api_changes.md)
 
-* [https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md](https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md)
+* [Api-conventions.md](/contributors/devel/sig-architecture/api-conventions.md)
 
 * [Pull-requests.md](https://github.com/kubernetes/community/blob/a74d906f0121c78114d79a3ac105aa2d36e24b57/contributors/devel/pull-requests.md#2-smaller-is-better-small-commits-small-prs) - should be updated to specifically call out API changes as important