Remove Fairing section

[80rian]

Resolves: #3721

Removing Fairing link as Fairing pages are removed from #3553.

[google-oss-prow[bot]]

Hi @80rian. Thanks for your PR.

I'm waiting for a kubeflow member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

[hbelmiro]

/ok-to-test

[rimolive]

/approve

[rimolive]

/cc @kubeflow/kubeflow-steering-committee

How can we proceed with documentation PRs? We have lots of OWNERS files spread in the repo, and only KSC members as the root OWNERS. If we want to ensure the Documentation phase can move on smoothly the Release Team need some autonomy to merge PRs.

[google-oss-prow[bot]]

@rimolive: GitHub didn't allow me to request PR reviews from the following users: kubeflow/kubeflow-steering-committee.

Note that only kubeflow members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to [this](https://github.com/kubeflow/website/pull/3722#issuecomment-2077041720): >/cc @kubeflow/kubeflow-steering-committee > >How can we proceed with documentation PRs? We have lots of OWNERS files spread in the repo, and only KSC members as the root OWNERS. If we want to ensure the [Documentation phase](https://github.com/kubeflow/community/blob/master/releases/handbook.md#documentation-3-weeks-starts-the-same-time-as-feature-freeze) can move on smoothly the Release Team need some autonomy to merge PRs. Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

[google-oss-prow[bot]]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 80rian, rimolive, terrytangyuan

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files: - ~~[content/en/docs/started/OWNERS](https://github.com/kubeflow/website/blob/master/content/en/docs/started/OWNERS)~~ [terrytangyuan] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment