fixing aliases

Author: abhatt-rh

content/contribute/implementation.adoc

@@ -4,6 +4,7 @@ menu:
     parent: Validated Pattern tiers
 title: Implementation requirements
 weight: 42
+aliases: /learn/implementation/
 aliases: /requirements/implementation/
 ---
 

content/contribute/maintained.adoc

@@ -4,7 +4,7 @@ menu:
     parent: Validated Pattern tiers
 title: Validated Patterns - Maintained tier
 weight: 45
-aliases: /requirements/maintained/
+aliases: /requirements/validated/
 ---
 
 :toc:
@@ -29,14 +29,14 @@ Each {maintained} pattern represents an ongoing maintenance, support, and testin
 
 For this reason we have designed the tiers and our processes to facilitate this to occur outside of the team by any sufficiently motivated party, including other parts of Red Hat, partners, and even customers.
 
-In limited cases, the {solution-name-upstream} team may consider taking on that work, however, it is recommended that you contact the team at least 4 weeks prior to the end of a given quarter for the necessary work to be considered as part of the following quarter's planning process.
+In limited cases, the {solution-name-upstream} team may consider taking on that work, however, it is recommended that you contact the team at least 4 weeks before the end of a given quarter for the necessary work to be considered as part of the following quarter's planning process.
 
 
 [id="requirements-maintained-tier"]
 == Requirements for the {maintained} tier
 
 The {maintained} patterns have deliverable and requirements in addition to those
-specified for the link:/requirements/tested/[Tested tier].
+specified for the link:/contribute/tested[Tested tier].
 
 The requirements are categorized as follows:
 

content/contribute/sandbox.adoc

@@ -5,7 +5,6 @@ menu:
 title: Validated Patterns - Sandbox tier
 weight: 43
 aliases: /requirements/community/
-aliases: /requirements/sandbox/
 ---
 
 :toc:
@@ -48,7 +47,7 @@ These are optional or desirable features, but their absence does not hinder the
 === Must
 A {sandbox} pattern must continue to meet the following criteria to remain in the {sandbox} tier:
 
-* A {sandbox} pattern must conform to the common technical link:/requirements/implementation/[implementation requirements].
+* A {sandbox} pattern must conform to the common technical link:/contribute/implementation/[implementation requirements].
 * A {sandbox} pattern must be able to be deployed onto a freshly deployed OpenShift cluster without prior modification or tuning.
 * A {sandbox} pattern must include a top-level README file that highlights the business problem and how the pattern solves it.
 * A {sandbox} pattern must include an architecture drawing. The specific tool or format is flexible as long as the meaning is clear.

content/contribute/test-artefacts.adoc

@@ -4,7 +4,6 @@ menu:
     parent: Validated Pattern tiers
 title: Testing Artefacts
 weight: 50
-aliases: /requirements/tested/
 ---
 
 :toc:

content/contribute/tested.adoc

@@ -4,7 +4,6 @@ menu:
     parent: Validated Pattern tiers
 title: Validated Patterns - Tested tier
 weight: 44
-aliases: /requirements/tested/
 ---
 
 :toc:
@@ -35,7 +34,7 @@ In limited cases, the {solution-name-upstream} team may consider taking on that
 [id="requirements-tested-tier"]
 == Requirements for the {tested} tier
 
-A {tested} patterns have deliverable and requirements in addition to those specified for the link:/requirements/sandbox/[Sandbox tier].
+A {tested} patterns have deliverable and requirements in addition to those specified for the link:/contribute/sandbox/[Sandbox tier].
 
 The requirements are categorized as follows: