docs: address nits

- Use `kubectl events` in favor of `kubectl get events`.
- Remove deleted `URL` field from `Status` examples of `GitRepository`
  v1.

Signed-off-by: Hidde Beydals <hidde@hhh.computer>

Author: hiddeco

docs/spec/v1/gitrepositories.md

@@ -81,7 +81,6 @@ You can run this example by saving the manifest into `gitrepository.yaml`.
        Status:                True
        Type:                  ArtifactInStorage
      Observed Generation:     1
-     URL:                     http://source-controller.source-system.svc.cluster.local./gitrepository/default/podinfo/latest.tar.gz
    Events:
      Type    Reason               Age   From               Message
      ----    ------               ----  ----               -------
@@ -670,7 +669,6 @@ Status:
     Status:                True
     Type:                  FetchFailed
   Observed Generation:     1
-  URL:                     http://source-controller.source-system.svc.cluster.local./gitrepository/default/gitrepository-sample/latest.tar.gz
 Events:
   Type     Reason                      Age                  From               Message
   ----     ------                      ----                 ----               -------
@@ -679,12 +677,12 @@ Events:
 
 #### Trace emitted Events
 
-To view events for specific GitRepository(s), `kubectl get events` can be used
-in combination with `--field-sector` to list the Events for specific objects.
-For example, running
+To view events for specific GitRepository(s), `kubectl events` can be used in
+combination with `--for` to list the Events for specific objects. For example,
+running
 
 ```sh
-kubectl get events --field-selector involvedObject.kind=GitRepository,involvedObject.name=<repository-name>
+kubectl events --for GitRepository/<repository-name>
 ```
 
 lists

docs/spec/v1beta2/buckets.md

@@ -896,12 +896,12 @@ Events:
 
 #### Trace emitted Events
 
-To view events for specific Bucket(s), `kubectl get events` can be used in
-combination with `--field-sector` to list the Events for specific objects.
-For example, running
+To view events for specific Bucket(s), `kubectl events` can be used in
+combination with `--for` to list the Events for specific objects. For example,
+running
 
 ```sh
-kubectl get events --field-selector involvedObject.kind=Bucket,involvedObject.name=<bucket-name>
+kubectl events --for Bucket/<bucket-name>
 ```
 
 lists

docs/spec/v1beta2/helmcharts.md

@@ -469,12 +469,12 @@ sion matching '9.*' found
 
 #### Trace emitted Events
 
-To view events for specific HelmChart(s), `kubectl get events` can be used in
-combination with `--field-selector` to list the Events for specific objects.
-For example, running
+To view events for specific HelmChart(s), `kubectl events` can be used in
+combination with `--for` to list the Events for specific objects. For example,
+running
 
 ```sh
-kubectl get events --field-selector involvedObject.kind=HelmChart,involvedObject.name=<chart-name>
+kubectl events --for HelmChart/<chart-name>
 ```
 
 lists

docs/spec/v1beta2/helmrepositories.md

@@ -598,12 +598,12 @@ Events:
 
 #### Trace emitted Events
 
-To view events for specific HelmRepository(s), `kubectl get events` can be used in
-combination with `--field-sector` to list the Events for specific objects.
-For example, running
+To view events for specific HelmRepository(s), `kubectl events` can be used in
+combination with `--for` to list the Events for specific objects. For example,
+running
 
 ```sh
-kubectl get events --field-selector involvedObject.kind=HelmRepository,involvedObject.name=<repository-name>
+kubectl events --for HelmRepository/<repository-name>
 ```
 
 lists

docs/spec/v1beta2/ocirepositories.md

@@ -682,12 +682,12 @@ Events:
 
 #### Trace emitted Events
 
-To view events for specific OCIRepository(s), `kubectl get events` can be used
-in combination with `--field-sector` to list the Events for specific objects.
-For example, running
+To view events for specific OCIRepository(s), `kubectl events` can be used
+in combination with `--for` to list the Events for specific objects. For
+example, running
 
 ```sh
-kubectl get events --field-selector involvedObject.kind=OCIRepository,involvedObject.name=<repository-name>
+kubectl events --for OCIRepository/<repository-name>
 ```
 
 lists