Not very practical, but good for understanding the OS: Everything is a file. Even your filesystem and harddrive is represented by a file (devicenode).
Back in the day, before things such as pulseaudio and equivalents became the norm, there was also such a file (it might still exist, idk) for your soundcard. By shoving the contents of a wav file directly into /dev/dsp, you could hear it as if it was played normally.
Unrelates to the above, in a terminal context it’s very handy to learn the concepts of STDIN, STDOUT, and STDERR, and how to manipulate these. I won’t go into it here, but whenever you see a bunch of commands strung together with redirects, < > | >>, that’s usually for sending the output (STDOUT) of one command somewhere else, such as to the input STDIN to another command.
I have exactly zero experience in what work a law office does, but I would think it’s mostly paperwork and email? If so you can do that at no startup costs.
Pick a distro (pop, mint, whatever), and install libreoffice or one of its many variants for offfice integration.
A common misconception is that linux involves a lot of coding. Sure, it can if you want to - all the hooks for programatical access are there, for example if you want to build shell scripts for automation. But you don’t need to. It’s just an option many linux users, myself included, like to take advantage of.
When it comes to convincing you, all I can say is this: It costs you nothing to try.