Updating cosign signing docs

content/en/about/overview.md

@@ -64,7 +64,6 @@ To use Sigstore, you must first install the client. Review the [Installation]({{
 - To get a quick view of how to use the program see [Quick Start]({{< relref "quickstart/quickstart-cosign">}})
 - To learn how to work with blobs, see [sign a blob]({{< relref "cosign/signing/signing_with_blobs">}})
 - To learn how to work with containers, see [sign a container]({{< relref "cosign/signing/signing_with_containers">}})
-- To use Gitsign, see [Sign Git commits with Gitsign]({{< relref "cosign/signing/gitsign">}})
 - To learn about verification, see [the importance of verification]({{< relref "about/the-importance-of-verification">}}) and [verify entries with Cosign]({{< relref "cosign/verifying/verify">}})
 - To learn about incorporating Sigstore into your CI System, see [our CI Quickstart]({{< relref "quickstart/quickstart-ci">}})
 

content/en/cosign/signing/git_support.md

@@ -23,14 +23,14 @@ To generate keys using a Git provider, you can use the `cosign generate-key-pair
 argument `github://` or `gitlab://`. For example:
 
 ```shell
-cosign generate-key-pair <some provider>://<owner>/<project>
+$ cosign generate-key-pair <some provider>://<owner>/<project>
 ```
 
 One little note here, if you prefer to use GitLab as a provider, you can specify the `ID` of the project instead of
 its name and owner, for example:
 
 ```shell
-cosign generate-key-pair gitlab://<project_id>
+$ cosign generate-key-pair gitlab://<project_id>
 ```
 
 The public key can be retrieved with:
@@ -78,6 +78,6 @@ feature is only available to GitLab. GitHub does not support it to fetch the sec
 You can also export the public key and verify it against that file:
 
 ```shell
-cosign public-key --key gitlab://<owner>/<project> > gitlab.pub
-cosign verify --key gitlab.pub gcr.io/user-vmtest2/demo
+$ cosign public-key --key gitlab://<owner>/<project> > gitlab.pub
+$ cosign verify --key gitlab.pub gcr.io/user-vmtest2/demo
 ```