'basic link' button and inline with number in Coach

[abhimnc]

Summary

Fixes #8629

view learners' button in Coach has incorrect styling
Button is a 'basic link' and inline with number, not on next line

References

#8629

Reviewer guidance

is it okay? Do I need modify more?

---

Testing checklist

• [-] Contributor has fully tested the PR manually
• [-] If there are any front-end changes, before/after screenshots are included
• Critical user journeys are covered by Gherkin stories
• Critical and brittle code paths are covered by unit tests

PR process

• [-] PR has the correct target branch and milestone
• [-] PR has 'needs review' or 'work-in-progress' ##label
• If PR is ready for review, a reviewer has been added. (Don't use 'Assignees')
• If this is an important user-facing change, PR or related issue has a 'changelog' label
• If this includes an internal dependency change, a link to the diff is provided

Reviewer checklist

• Automated test coverage is satisfactory
• PR is fully functional
• PR has been tested for accessibility regressions
• External dependency files were updated if necessary (yarn and pip)
• Documentation is updated
• Contributor is in AUTHORS.md

[rtibbles]

You have based your work here off the develop branch, which includes commits not in the release-v0.15.x branch.

To fix this, I'd recommend making sure your local copy of release-v0.15.x is up to date, and then do the following:

git checkout my-awesome-changes
git rebase -i release-v0.15.x

The second command here will open a text editor and prompt you with a list of commits. You should mark all the commits as 'drop' except your added alignment space commit.

Once that is done, you should force push to the remote my-awesome-changes branch, which will update this PR.

[indirectlylit]

Thank you!

A couple small changes requested

[indirectlylit]

Please revert the changes to package.json and yarn.lock as they are not directly related to this fix.

I've opened a follow-up issue related to the warnings you were seeing here: #8728

[abhimnc]

I am not able to revert changes to package.json and yarn.lock by git commands. should i delete this branch and create a new one with applied changes.

[indirectlylit]

Hi – I force-pushed an update to your branch which keeps only the relevant files.

For future reference, it's possible to break a previous commit in pieces and choose only portions of that commit using an interactive rebase.

See for example: https://stackoverflow.com/questions/6217156/break-a-previous-commit-into-multiple-commits

[indirectlylit]

looks good!