Fix links and update access/request issue link

src/handbook/development/ops/index.md

@@ -0,0 +1,7 @@
+---
+navTitle: Platform Ops
+---
+
+ - [Observability](./observability.md)
+ - [Staging Environment](./staging.md)
+ - [Production Environment](./production.md)

src/handbook/development/ops/production.md

@@ -7,7 +7,7 @@ navTitle: Production Environment
 Our production environment runs in `EU-West-1` in a dedicated AWS account.
 
 Access to the AWS account is restricted and not generally available. If you believe
-you have a need to access the AWS account, raise an issue in [CloudProject](https://github.com/FlowFuse/CloudProject)
+you have a need to access the AWS account, raise an [Access/Permission Request issue](https://github.com/FlowFuse/admin/issues/new/choose)
 and assign to the CTO for review.
 
 ## Using production

src/handbook/development/ops/staging.md

@@ -18,9 +18,8 @@ The deploy action can be monitored [here](https://github.com/FlowFuse/helm/actio
 
 ## AWS Account
 
-It uses a separate AWS account ending in ..9937. The services are running in EU-West-1.
 Access to the AWS account is restricted and not generally available. If you believe
-you have a need to access the AWS account, raise an issue in [CloudProject](https://github.com/FlowFuse/CloudProject)
+you have a need to access the AWS account, raise an [Access/Permission Request issue](https://github.com/FlowFuse/admin/issues/new/choose)
 and assign to the CTO for review.
 
 ## Email
@@ -38,7 +37,7 @@ We have enabled a small list of mailinator.com based email addresses for the pur
 of short-lived testing of sign-up and user management.
 
 The inboxes for these email addresses are publicly accessible if known, so the list
-is available on this private issue: https://github.com/FlowFuse/CloudProject/issues/135
+is available on [this private issue](https://github.com/FlowFuse/CloudProject/issues/135).
 
 ## Using staging
 

src/handbook/development/packaging.md

@@ -167,11 +167,11 @@ Package numbers should follow the Semantic Versioning Scheme as laid out on [sem
 
 Each component will stay in step with the core flowforge/flowforge release numbering for `major.minor` but will increment their own `fix` values as needed. e.g. On release of v0.2.0 all components will tag and release v0.2.0, but can independently release v0.2.1 as needed.
 
-Major and minor releases will follow the schedule laid out in the [Cadence](../releases/planning#cadence) section of the handbook.
+Major and minor releases will follow the schedule laid out in the [Cadence](./releases/planning#cadence) section of the handbook.
 
 A Fix release can be made at any time, depending on the best judgement of the engineer making the fix but requires a review by another team member.
 
-The process for making a release is documented [here](../releases/process.md).
+The process for making a release is documented [here](./releases/process.md).
 
 ### Adding NPM packages to Stacks