Updating public docs to reflect GitHub Connections in Platform Hub capabilities and limitations (#3062)

Author: felixi-octopus

src/pages/docs/platform-hub/templates/process-templates/troubleshooting.md

@@ -155,7 +155,7 @@ See [CreateProcessTemplateUsageStep](https://github.com/OctopusDeploy/OctopusDep
 
 ### GitHub Connections
 
-The GitHub Connection is not supported in Platform Hub. Only usernames and PATs.
+GitHub Connections is supported in Platform Hub, but it can only be used to configure Platform Hub version control. It can't be used on steps in templates.
 
 ### Losing access to an Octopus Enterprise license
 
@@ -181,7 +181,7 @@ To reference output variables from process template steps, add `.ProcessTemplate
 
 When referencing an output variable in a step **inside a process template**, use the format:
 
-```text
+```powershell
 Octopus.ProcessTemplate.Action[StepName].Output.PropertyName
 ```
 

src/pages/docs/projects/version-control/github/index.md

@@ -64,6 +64,8 @@ To connect a repository, you must be an administrator of the repository on GitHu
 
 You can currently use GitHub App Connections to connect to Configuration as Code projects. This removes the need for using Personal Access Tokens to connect to GitHub repositories, and allows users to commit as their GitHub users (rather than using a shared account).
 
+You can also define GitHub Connections in [Platform Hub](/docs/platform-hub). GitHub Connections defined in Platform Hub can only be used to configure Platform Hub's version control settings and can't be used in spaces.
+
 ## Requested Permissions
 
 There are specific GitHub permissions that the Octopus GitHub App requests in order to perform it's tasks.