fix: resource config links

Fix redirects to resource configuration

Signed-off-by: Noel Georgi <[email protected]>

website/content/docs/v0.2/Getting Started/import-machines.md

@@ -26,7 +26,7 @@ credentials to communicate).
 > Note: if you are running in a safe environment, you can configure Sidero to
 > automatically accept new machines.
 
-For more information on server acceptance, see the [server docs](/docs/v0.3/configuration/servers/#server-acceptance).
+For more information on server acceptance, see the [server docs](/docs/v0.3/resource-configuration/servers/#server-acceptance).
 
 ## Create ServerClasses
 
@@ -41,7 +41,7 @@ This is analogous to cloud providers using such classes as `m3.large` or
 `c2.small`, but the names are free-form and only need to make sense to you.
 
 For more information on ServerClasses, see the [ServerClass
-docs](/docs/v0.3/configuration/serverclasses/).
+docs](/docs/v0.3/resource-configuration/serverclasses/).
 
 ## Hardware differences
 
@@ -67,7 +67,7 @@ those patches will be applied to the final machine configuration for those
 nodes without having to know anything about those nodes at the allocation level.
 
 For examples of install disk patching, see the [Installation Disk
-doc](/docs/v0.3/configuration/servers/#installation-disk).
+doc](/docs/v0.3/resource-configuration/servers/#installation-disk).
 
 For more information about patching in general, see the [Patching
 Guide](/docs/v0.3/guides/patching).

website/content/docs/v0.3/Getting Started/import-machines.md

@@ -26,7 +26,7 @@ credentials to communicate).
 > Note: if you are running in a safe environment, you can configure Sidero to
 > automatically accept new machines.
 
-For more information on server acceptance, see the [server docs](/docs/v0.3/configuration/servers/#server-acceptance).
+For more information on server acceptance, see the [server docs](/docs/v0.3/resource-configuration/servers/#server-acceptance).
 
 ## Create ServerClasses
 
@@ -41,7 +41,7 @@ This is analogous to cloud providers using such classes as `m3.large` or
 `c2.small`, but the names are free-form and only need to make sense to you.
 
 For more information on ServerClasses, see the [ServerClass
-docs](/docs/v0.3/configuration/serverclasses/).
+docs](/docs/v0.3/resource-configuration/serverclasses/).
 
 ## Hardware differences
 
@@ -67,7 +67,7 @@ those patches will be applied to the final machine configuration for those
 nodes without having to know anything about those nodes at the allocation level.
 
 For examples of install disk patching, see the [Installation Disk
-doc](/docs/v0.3/configuration/servers/#installation-disk).
+doc](/docs/v0.3/resource-configuration/servers/#installation-disk).
 
 For more information about patching in general, see the [Patching
 Guide](/docs/v0.3/guides/patching).

website/content/docs/v0.3/Guides/bootstrapping.md

@@ -146,7 +146,7 @@ Servers can be accepted by issuing a patch command like:
 kubectl patch server 00000000-0000-0000-0000-d05099d33360 --type='json' -p='[{"op": "replace", "path": "/spec/accepted", "value": true}]'
 ```
 
-For more information on server acceptance, see the [server docs](/docs/v0.3/configuration/servers).
+For more information on server acceptance, see the [server docs](/docs/v0.3/resource-configuration/servers).
 
 ## Create Management Plane
 

website/content/docs/v0.3/Guides/first-cluster.md

@@ -99,7 +99,7 @@ Servers can be accepted by issuing a patch command like:
 kubectl patch server 00000000-0000-0000-0000-d05099d33360 --type='json' -p='[{"op": "replace", "path": "/spec/accepted", "value": true}]'
 ```
 
-For more information on server acceptance, see the [server docs](/docs/v0.3/configuration/servers).
+For more information on server acceptance, see the [server docs](/docs/v0.3/resource-configuration/servers).
 
 ## Create the Cluster
 

website/content/docs/v0.3/Overview/resources.md

@@ -90,21 +90,21 @@ These define a desired deployment environment for Talos, including things like w
 Sidero allows you to define a default environment, as well as other environments that may be specific to a subset of nodes.
 Users can override the environment at the `ServerClass` or `Server` level, if you have requirements for different kernels or kernel parameters.
 
-See the [Environments](/docs/v0.3/configuration/environments/) section of our Configuration docs for examples and more detail.
+See the [Environments](/docs/v0.3/resource-configuration/environments/) section of our Configuration docs for examples and more detail.
 
 #### `Servers`
 
 These represent physical machines as resources in the management plane.
 These `Servers` are created when the physical machine PXE boots and completes a "discovery" process in which it registers with the management plane and provides SMBIOS information such as the CPU manufacturer and version, and memory information.
 
-See the [Servers](/docs/v0.3/configuration/servers/) section of our Configuration docs for examples and more detail.
+See the [Servers](/docs/v0.3/resource-configuration/servers/) section of our Configuration docs for examples and more detail.
 
 #### `ServerClasses`
 
 `ServerClasses` are a grouping of the `Servers` mentioned above, grouped to create classes of servers based on Memory, CPU or other attributes.
 These can be used to compose a bank of `Servers` that are eligible for provisioning.
 
-See the [ServerClasses](/docs/v0.3/configuration/serverclasses/) section of our Configuration docs for examples and more detail.
+See the [ServerClasses](/docs/v0.3/resource-configuration/serverclasses/) section of our Configuration docs for examples and more detail.
 
 ### Metal Metadata Server
 
@@ -115,4 +115,4 @@ While the metadata server does not present unique CRDs within Kubernetes, it's i
 The metadata server may be familiar to you if you have used cloud environments previously.
 Using Talos machine configurations created by the Talos Cluster API bootstrap provider, along with patches specified by editing `Server`/`ServerClass` resources or `TalosConfig`/`TalosControlPlane` resources, metadata is returned to servers who query the metadata server at boot time.
 
-See the [Metadata](/docs/v0.3/configuration/metadata/) section of our Configuration docs for examples and more detail.
+See the [Metadata](/docs/v0.3/resource-configuration/metadata/) section of our Configuration docs for examples and more detail.