Update evaluate-expressions-in-workflows-and-actions.md

[silky-x0]

Explained how operators are used.

issue-#37006

Why:

Which operator is a ternary exactly? #37006

What's being changed (if available, include any code snippets, screenshots, or gifs):

Check off the following:

• [ x] A subject matter expert (SME) has reviewed the technical accuracy of the content in this PR. In most cases, the author can be the SME. Open source contributions may require an SME review from GitHub staff.
• [x ] The changes in this PR meet the docs fundamentals that are required for all content.
• [x ] All CI checks are passing and the changes look good in the review environment.

[welcome]

Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

[github-actions]

How to review these changes 👓

Thank you for your contribution. To review these changes, choose one of the following options:

• Spin up a codespace
• Set up a local development environment

A Hubber will need to deploy your changes internally to review.

Table of review links

Note: Please update the URL for your staging server or codespace.

The table shows the files in the content directory that were changed in this pull request. This helps you review your changes on a staging server. Changes to the data directory are not included in this table.

Source	Review	Production	What Changed
actions/writing-workflows/choosing-what-your-workflow-does/evaluate-expressions-in-workflows-and-actions.md	fpt ghec ghes@ 3.173.163.153.143.13	fpt ghec ghes@ 3.173.163.153.143.13

Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server

🤖 This comment is automatically generated.

[Sharra-writes]

@silky-x0 Thanks for opening a PR to address this issue! I'll get it triaged for review.

[github-actions]

Thanks for opening a pull request! We've triaged this issue for technical review by a subject matter expert 👀

[silky-x0]

@TRIXMI could you please provide more info what you trying to say?

[Sharra-writes]

@silky-x0 It's spam, probably a bot. We get a lot of them in here. Don't worry about it, I blocked it. If we start seeing more, I'll lock the conversation. Sometimes for whatever reason they all just pile into one specific issue or PR.

[silky-x0]

@Sharra-writes okey, does it usually take this long to close PR related to DOCS?

[Sharra-writes]

@silky-x0 We're a small team and for something that needs both an SME and writer review (as this does and will), I'm afraid I'm going to be thanking you for your patience a lot. 😅 I will keep you updated as we make our way through the review process, though.

And just to get it started, I do appreciate your patience. 💛

[silky-x0]

@Sharra-writes no worries, patience is key.

[Sharra-writes]

@silky-x0 Okay, so, here's what's going on: I got a review from one writer who wanted to keep just the change to line 112, without adding in the example you wrote. He recommended a review from another writer to confirm, but that writer has been swamped, so I haven't been able to get him to take a look. So. We have a review from one writer, which is technically enough. Either we can go with his suggestion and get rid of the example, or I can wait to confirm with the other writer whenever he has time, and see if he has a different answer.

[silky-x0]

@Sharra-writes I guess what he said will suffice because most the people coming here would obviously know how OR, AND works. I'll make changes then.

[silky-x0]

@Sharra-writes Everything's done I've removed those lines.

[Sharra-writes]

@silky-x0 Beautiful. Thank you again for being patient with us, and I'll get this merged as soon as checks are passing!

[github-actions]

Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues ⚡