Question : SQL 2005 Restore remains in restoring mode

I am trying to implement a mirror in SQL 2005 with Principal, Mirror and Witness.

I have proceeded to backing  up the database and transaction logs, (.bak and .trn) and subsequently resotre (with no recovery as an option) on the Standby SQL server.

The SQL Log indicates that the restore has completed for both jobs, and so does the Application Log.  However the database remains in the database snapshots section and continues to indicate that it is in restoring mode.  

I have deleted this database and tried several times, all with the same results. The Database is 30MB in size.

Answer : SQL 2005 Restore remains in restoring mode

Excerpt from Books Online -

"When specifying the NORECOVERY option, the database is not usable in this intermediate, nonrecovered state.

When used with a file or filegroup restore operation, NORECOVERY forces the database to remain in the restoring state after the restore operation. This is useful in either of these situations:

A restore script is being run and the log is always being applied.

A sequence of file restores is used and the database is not intended to be usable between two of the restore operations. "

When you use NORECOVERY, you are basically instructing the SQL Server not to allow it to be use. I'd believe the last transaction log restored should be RESTORED WITH RECOVERY?