fix plan persistence documentation

Author: motatoes

docs/ce/features/plan-persistence.mdx

@@ -40,6 +40,11 @@ The value of `$DIGGER_OUT` defaults to `$RUNNER_TEMP/digger-out.log`; you can ch
 
 ## Overriding plan commands
 
+<Note>
+    This is an advanced usecase if you want to specify an entirely custom command during plan and apply phases. If you only want to use
+    plan artefacts the easiest way would be to simply configure [plan artefacts persistence](/ce/howto/plan-artefacts) and you would not need to perform
+    a complete override of the plan and apply commands.
+</Note>
 You can add extra arguments to the plan command by setting the `extra_args` key in the `steps` section of the `plan` command.
 
 However in some cases if you wish to override the plan command entirely you can do it by excluding the plan in the steps and having your command specified in the run like so:

docs/ce/howto/custom-commands.mdx

@@ -1,14 +1,25 @@
 ---
-title: "Store plans in a Bucket"
+title: "Plan artefacts"
 ---
 
+Digger can be used to store plan artefacts during the plan phase and make them available for use during the apply phase. Once plan artefacts is configured and uploaded during the plan phase
+it will automatically be used during the apply phase. Once one of the below artefacts is configured successfully there is no additional configuration needed on your end to achieve apply-time artefact reuse.
+
 ### Github 
 Digger can use Github Artifacts to store `terraform plan` outputs. In order to enable it you can set the following argument in digger_workflow.yml:
 
 ```
 upload-plan-destination: github
 ```
 
+<Warning>
+    Github plan artefacts as a destination is currently deprecated due to a change in Github API. For more information see [this issue](https://github.com/diggerhq/digger/issues/1702).
+</Warning>
+
+<Alert>
+    sadfasdf
+</Alert>
+
 ### GCP 
 You can also configure plan outputs to be uploaded to GCP Buckets instead. This is handy in case you want your plan outputs to stay within your organisation's approved storage providers for security or compliance reasons.
 

docs/ce/howto/store-plans-in-a-bucket.mdx renamed to docs/ce/howto/plan-artefacts.mdx

@@ -71,7 +71,6 @@
         "ce/features/concurrency",
         "ce/features/layering",
         "ce/features/pr-level-locks",
-        "ce/features/plan-persistence",
         "ce/features/private-runners",
         "ce/features/drift-detection",
         "ce/features/rbac",
@@ -104,7 +103,7 @@
         "ce/howto/policy-overrides",
         "ce/howto/project-level-roles",
         "ce/howto/segregate-cloud-accounts",
-        "ce/howto/store-plans-in-a-bucket",
+        "ce/howto/plan-artefacts",
         "ce/howto/trigger-directly",
         "ce/howto/using-checkov",
         "ce/howto/using-infracost",