Skip to content

docs: fix inline code style in readme #1083

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

hatamiarash7
Copy link

Proposed changes

Fix this little problem for an inline code style.

Checklist

Before creating a PR, run through this checklist and mark each as complete.

  • I have read the CONTRIBUTING guide
  • I have proven my fix is effective or that my feature works
  • I have checked that all unit tests pass after adding my changes
  • I have ensured the README is up to date
  • I have rebased my branch onto main
  • I will ensure my PR is targeting the main branch and pulling from my branch on my own fork

Signed-off-by: Arash Hatami <hatamiarash7@gmail.com>
@hatamiarash7 hatamiarash7 requested a review from a team as a code owner June 7, 2025 17:31
Copy link

nginx-bot bot commented Jun 7, 2025

Hi @hatamiarash7! Welcome to the project! 🎉

Thanks for opening this pull request!
Be sure to check out our Contributing Guidelines while you wait for someone on the team to review this.

@nginx-bot nginx-bot bot added the community Issues or PRs opened by an external contributor label Jun 7, 2025
@github-actions github-actions bot added the documentation Pull requests/issues for documentation label Jun 7, 2025
Copy link

github-actions bot commented Jun 7, 2025

✅ All required contributors have signed the F5 CLA for this PR. Thank you!
Posted by the CLA Assistant Lite bot.

@hatamiarash7
Copy link
Author

I have hereby read the F5 CLA and agree to its terms

@hatamiarash7
Copy link
Author

You made the right point. It's fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community Issues or PRs opened by an external contributor documentation Pull requests/issues for documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants