docs: fix long dead links to architecture allocation detail.

website/content/docs/concepts/workload-identity.mdx

@@ -172,7 +172,7 @@ Consul and Vault can be configured to accept workload identities from Nomad for
 authentication. Refer to the [Consul][consul_int] and [Vault][vault_int]
 integration pages for more information.
 
-[allocation]: /nomad/docs/concepts/architecture#allocation
+[allocation]: /nomad/docs/glossary#allocation
 [identity-block]: /nomad/docs/job-specification/identity
 [jobspec_consul]: /nomad/docs/job-specification/consul
 [jobspec_consul_ns]: /nomad/docs/job-specification/consul#namespace

website/content/docs/networking/index.mdx

@@ -24,7 +24,7 @@ Nomad differs from other tools in this aspect.
 ## Allocation networking
 
 The base unit of scheduling in Nomad is an
-[allocation](/nomad/docs/concepts/architecture#allocation), which means that all
+[allocation](/nomad/docs/glossary#allocation), which means that all
 tasks in the same allocation run in the same client and share common resources,
 such as disk and networking. Allocations can request access to network
 resources, such as ports, using the