✔️ Linting Passed

All linting checks passed. Your pull request is in excellent shape! ☀️

_{Generated for commit: 2f915e4. Link to the linter CI: here}

Sorry, I updated 4 times, because I did not understand the update work flow.
I will never do the meaningless multiple update.

A message "This branch is out-of-date with the base branch" appears.
But doing "Update branch" results in redoing some checks.
Should I do "Update branch"?

Thanks for the PR @hiramatsuyuusuke. Maybe you can convert the section 1.4.6.3. Using Python functions as kernels into a separate dropdown and then move the example out of it and after the Gram matrix dropdown, yet inside the 1.4.6.2. Custom Kernels. I hope that is clear, but if I didn't express correctly please let me know :)

Should I do "Update branch"?

In general you don't have do it, except is the CI is failing on our side or if the file concerned by the PR has conflicts. In any other case triggering the tests just consumes computational resources.

Thanks for the review and advice, @ArturoAmorQ.
I'm working on it.

And if there are no mistakes, I follow these steps:
When I complete it, I will push it to my fork branch.
Next, I will run "Update branch" botton on this page.

To reviewer @ArturoAmorQ.
I made some changes. Please confirm the these changes.

I made a separate dropdown Using Python functions as kernels . And I moved the example after the Gram matrix dropdown. Then two dropdowns and one example are inside the 1.4.6.2. Custom Kernels.

Additionally, I trigger the tests, because the file was changed. Were these tests necessary?

Additionally, I trigger the tests, because the file was changed. Were these tests necessary?

Sorry for taking so long to answer. Triggering the tests is not necessary if you changed the file, it is only necessary if the file was changed by another PR and it is generating a conflict.

You can also re-trigger the tests if they are failing and the error message does not seem related to your changes.