fix(docs): add backticks to fix Markdown formatting
Change-Id: I479da776c2ba471debea2b7257d10cf90be81a1e
Signed-off-by: Demi Marie Obenour <demiobenour@gmail.com>
diff --git a/docs/SchedulerExpectations.md b/docs/SchedulerExpectations.md
index 851fbd6..c25018f 100644
--- a/docs/SchedulerExpectations.md
+++ b/docs/SchedulerExpectations.md
@@ -51,7 +51,7 @@
A message has been sent by the vCPU. If the recipient is the scheduler VM itself
then it can handle it as it pleases. Otherwise the scheduler MUST run a vCPU
from the recipient VM and priority SHOULD be given to those vCPUs that are
-waiting for a message. The scheduler should call FFA_RUN again on the sending
+waiting for a message. The scheduler should call `FFA_RUN` again on the sending
VM as usual.
### `FFA_RX_RELEASE`
@@ -59,7 +59,7 @@
The vCPU has made the mailbox writable and there are pending waiters. The
scheduler MUST call `hf_mailbox_waiter_get()` repeatedly and notify all waiters
by injecting an `HF_MAILBOX_WRITABLE_INTID` interrupt. The scheduler should call
-FFA_RUN again on the sending VM as usual.
+`FFA_RUN` again on the sending VM as usual.
### `HF_FFA_RUN_WAIT_FOR_INTERRUPT`
@@ -79,7 +79,7 @@
The vCPU has aborted triggering the whole VM to abort. The scheduler MUST treat
this the same as `FFA_INTERRUPT` for all the other vCPUs of the VM. For this
-vCPU the scheduler SHOULD either never call FFA_RUN on the vCPU again, or treat
+vCPU the scheduler SHOULD either never call `FFA_RUN` on the vCPU again, or treat
it the same as `HF_FFA_RUN_WAIT_FOR_INTERRUPT`.
#### Any other error code