📚 Sync docs from alaudadevops/connectors-operator on 549295a47a43664e6ff0db322ed61e4fd4e07388

Source: fix docs lint error (#445)
Author: chengjingtao
Ref: refs/heads/release-1.6
Commit: 549295a47a43664e6ff0db322ed61e4fd4e07388

This commit automatically syncs documentation changes from the source-docs repository.

🔗 View source commit: https://github.com/alaudadevops/connectors-operator/commit/549295a47a43664e6ff0db322ed61e4fd4e07388
🤖 Synced on 2025-12-15 04:36:12 UTC

Author: edge-katanomi-app2[bot]

.github/SYNC_INFO.md

@@ -1,10 +1,10 @@
 # Documentation Sync Information
 
-- **Last synced**: 2025-12-12 11:10:28 UTC
+- **Last synced**: 2025-12-15 04:36:12 UTC
 - **Source repository**: alaudadevops/connectors-operator
-- **Source commit**: [1c58b39b23d088ba601f6c16ebf000fe2a4a3c6b](https://github.com/alaudadevops/connectors-operator/commit/1c58b39b23d088ba601f6c16ebf000fe2a4a3c6b)
+- **Source commit**: [549295a47a43664e6ff0db322ed61e4fd4e07388](https://github.com/alaudadevops/connectors-operator/commit/549295a47a43664e6ff0db322ed61e4fd4e07388)
 - **Triggered by**: edge-katanomi-app2[bot]
-- **Workflow run**: [#65](https://github.com/alaudadevops/connectors-operator/actions/runs/20164913260)
+- **Workflow run**: [#67](https://github.com/alaudadevops/connectors-operator/actions/runs/20220652421)
 
 ## Files synced:
 - docs/

docs/en/connectors-harbor/concepts/harbor_connectorclass.mdx

@@ -90,7 +90,7 @@ For example:
 
 For security best practices, we recommend creating credentials with minimal required permissions. When additional privileges are needed, create separate Connectors with more privileged secret and use namespace isolation to control which users can access each Connector.
 
-### Proxy and Configuration Capabilities
+### Proxy and Configuration Capabilities \{#proxy_and_configuration_capabilities}
 
 The Harbor Connector provides proxy capabilities to enable secure access to Harbor registries.
 

docs/en/connectors-harbor/how_to/using_harbor_connector_in_k8s.mdx

@@ -93,9 +93,9 @@ volumes:
       configuration.names: "config"
 ```
 
-> For the configuration information of the Harbor ConnectorClass, please refer to [Harbor ConnectorClass Configuration](../concepts/harbor_connectorclass.mdx#configuration).
+> For the configuration information of the Harbor ConnectorClass, please refer to [Harbor ConnectorClass Configuration](../concepts/harbor_connectorclass.mdx#proxy_and_configuration_capabilities).
 
-3. Configuring the client CLI to support pushing to insecure registries
+1. Configuring the client CLI to support pushing to insecure registries
 
 Since the proxy service provided by the connector uses HTTP protocol, it is necessary to configure `insecure-registries` on the client. Different clients have different configuration methods:
 
@@ -121,4 +121,4 @@ For example:
 ## More
 
 - [Using Harbor Connector to Build Images in K8S Job](./using_harbor_connector_in_k8s_job.mdx)
-- [Using Harbor Connector to Build Images in Tekton Pipeline](./using_harbor_connector_in_tekton_pipeline.mdx)
+- [Using Harbor Connector to Build Images in Tekton Pipeline](./using_harbor_connector_forward_proxy_in_tekton_pipeline.mdx)

docs/en/connectors-oci/trouble_shooting/csi_driver_issues.mdx

@@ -212,4 +212,4 @@ spec:
 - [OCI Connector Quick Start](../quick_start.mdx)
 - [Connector Status Troubleshooting](../../connectors/trouble_shooting/connectors_issues.mdx)
 - [Using OCI Connector in Kubernetes Workloads](../how_to/using_oci_connector_in_k8s.mdx)
-- [Using OCI Connector in Tekton Pipeline](../how_to/using_oci_connector_in_tekton_pipeline.mdx) 
+- [Using OCI Connector in Tekton Pipeline](../how_to/using_oci_connector_forward_proxy_in_tekton_pipeline.mdx)

docs/en/connectors/concepts/resource_interface.mdx

@@ -419,6 +419,8 @@ The following ConnectorClass configuration defines the `GET /git/gitrefs` API wi
 - The `search` parameter is set to `${current.search}` for filtering results
 - The response `items` array is mapped to select options, using `name` for both label and value
 
+example:
+
 ``` yaml
 kind: ConnectorClass
 spec:
@@ -470,6 +472,8 @@ Once the API is defined in ConnectorClass, reference it in your ResourceInterfac
 - `urn:alm:descriptor:widgets:select` to specify the widget type
 - `schema:openapi:context.connectorClass.spec.api.openapi:<operationId>` to reference the API definition in the ConnectorClass
 
+for example:
+
 ```yaml
 kind: ResourceInterface
 metadata: