Data Guard : Standby Redo Log CONFUSION

Question

Trying to set up test Standby db on 10.2.0
I am well confused about below step 3.1.3, how is the normal redo linked with standby redo, should standby not be members of orginal redo groups?
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/create_ps.htm#i1225703
Original redo logs:
SQL>  select * from v$log;
    GROUP#    THREAD#  SEQUENCE#      BYTES    MEMBERS ARC STATUS           FIRST_CHANGE# FIRST_TIME
         1          1         28   52428800          1 YES INACTIVE                375136 22-NOV-07
         2          1         29   52428800          1 YES INACTIVE                375138 22-NOV-07
         3          1         30   52428800          1 NO  CURRENT                 375143 22-NOV-07I added below from notes:
ALTER DATABASE ADD STANDBY LOGFILE GROUP 10
('/u01/oracle/oradata/db01/redo01_stb.log') SIZE 50M;
ALTER DATABASE ADD STANDBY LOGFILE GROUP 11
('/u02/oracle/oradata/db01/redo02_stb.log') SIZE 50M;
ALTER DATABASE ADD STANDBY LOGFILE GROUP 12
('/u03/oracle/oradata/db01/redo03_stb.log') SIZE 50M;After few alter system switch logfile; I still have:
    GROUP#    THREAD#  SEQUENCE# ARC STATUS
        10          0          0 YES UNASSIGNED
        11          0          0 YES UNASSIGNED
        12          0          0 YES UNASSIGNEDAll are UNASSIGNED, should one standby group not be ACTIVE like the above link shows.
Many think for any help

Answer 1

First things first:
From the Docs.:
"Minimally, the configuration should have one more standby redo log file group than the number of online redo log file groups on the primary database. However, the recommended number of standby redo log file groups is dependent on the number of threads on the primary database. Use the following equation to determine an appropriate number of standby redo log file groups:
(maximum number of logfiles for each thread + 1) * maximum number of threads
Using this equation reduces the likelihood that the primary instance's log writer (LGWR) process will be blocked because a standby redo log file cannot be allocated on the standby database. For example, if the primary database has 2 log files for each thread and 2 threads, then 6 standby redo log file groups are needed on the standby database."
You are 1 short!