"Thanks for trying to help. I really appreciate it! ..."

While I'm happy to help, you need to help us as well. Posting all your text and code in a single block without any markup makes it very difficult to read. Put your text into paragraphs within <p>...</p> tags and your code within <code>...</code> tags. Details can be found in (or linked from) "Writeup Formatting Tips"; and "How do I change/delete my post?" explains how to fix what you've already done.

After putting your code into some sort of readable layout, it would appear that what I'm talking about is pretty much the same thing that you're learning about:

$ perl -Mstrict -Mwarnings -E '
    my $numone;
    my $numtwo;
    print "Please enter first number ";
    $numone = <STDIN>;
    print "Please enter second number ";
    $numtwo = <STDIN>;

    #if ($numone < $numtwo); { <--- WRONG: no semicolon here
    if ($numone < $numtwo) {
        print $numone;
        print $numtwo;
    }
    # elsif { <--- WRONG: should be else
    else {
        print $numtwo;
        print $numone;
    }

    print "Hit enter when done: "; <>;
'
Please enter first number 456
Please enter second number 123
123
456
Hit enter when done:
[download]

So, in this context, "<>" is just a short-hand form of "<STDIN>": see "perlop: I/O Operators" for the full story. Also, I don't assign the user input to a variable because I don't want it and, in fact, don't really care what the user enters. This works the same:

$ perl -Mstrict -Mwarnings -E '
    ... previous code unchanged ...

    print "Hit enter when done: "; <STDIN>;
'
Please enter first number 456
Please enter second number 123
123
456
Hit enter when done: I'm all done with this!
[download]

"I think I know what the problem is. Apparently when naming your files you should not use spaces. When I changed the file name and removed my spaces it ran."

I generally refrain from using spaces in filenames because spaces are already used to separate the program name from switches, input files, and so on: basically it's a real nuisance that's easily avoided. However, it's not actually illegal and you will encounter third-party filenames that do include spaces: when you do, just quote them (i.e. "some filename with spaces"). I'd tend to write that filename as some_filename_without_spaces, which is just as easy to read but has none of the associated problems.

"Now I know for sure I'll never be a programmer because I have LOTS of errors:-)"

You'll learn a lot more from making mistakes and fixing them, than if you wrote all your code perfectly. What's more, sorry to be the one to tell you this but, don't worry at all about mistakes after only 2 days of coding: you'll still be making mistakes with 20 years experience under your belt.

Also, don't worry too much about the number of errors: a simple mistake like a missing semicolon at the end of a statement, or using the wrong quote to terminate a string, can result in dozens of errors. When I frst ran the code you posted, I got:

syntax error at -e line 9, near ");"
Unmatched right curly bracket at -e line 12, at end of line
syntax error at -e line 12, near "}"
syntax error at -e line 16, near "}"
Execution of -e aborted due to compilation errors.
[download]

But, as you can see from my previous post, there were only two small errors that were easily fixed.