No.. It's a very common programming concept. You open a file folder.. all the items in the file folder are 'children' of the parent folder. It's the same with running processes launching child processes. The terms for ending processes abruptly all sound like murder. There's lots of commands embedded in different operating systems such as 'kill' 'terminate' etc.. If your process is using a dangerous amount of memory (about to cause the whole system to lock up), it needs to kill some of its processes or it will crash similar to a Windows blue screen..

Not really, it's just the terminology used. It comes from family trees. Which are also Binary trees.

When a process spawns a process you call it a parent and child. Because the parent process spawned the child process. You do things to processes sometimes like kill them or fork them.... Seriously this is just normal computing terms. I had a professor that made up all kinds of jokes when he explained stuff. Like when a child process replaces a parent process.