Squashed 'motor_control' changes from 0b7b5bf..e6747aa (#973)

e6747aa Merge pull request #348 from yuanqian/CR-1179649
d190c35 fix CR-1179649

Co-authored-by: sdausr <[email protected]>

Author: 2 people

motor_control/docs/src/guide_L1/IPs/pwm_gen.rst

@@ -55,7 +55,7 @@ As it is shown in the above pictures, the entire SVPWM have 3 functions. PWM_GEN
 
 * stt_pwm_cycle: this parameter is to monitor the status of pwm_cycle length, which is supposed to be clk_freq/pwm_freq.
 
-* sampling ii: flag "[-ii <sampling II>]". The ii (iteration interval) determines the sampling rate of the input. The default value is 1. 
+* sampling ii: flag "[-ii <sampling II>]". The ii (initiation interval) determines the sampling rate of the input. The default value is 1. 
 
 Profiling 
 ============

motor_control/docs/src/guide_L1/IPs/svpwm_duty.rst

@@ -55,7 +55,7 @@ As it is shown in the aboved pictures, the entire SVPWM_DUTY have five configura
 
 * dead_cycles: flag "[-dead <dead cycles>]". The dead_cycles determines the transit time between the switch on/off. The switches pair shall not simultaneously be switching on and off, in terms of the danger of overloaded transient currents on the bridge. It may incur the systematic turbulence and cause serious problem. The default value of dead_cycles is 10.  
 
-* sampling ii: flag "[-ii <sampling II>]". The ii (iteration interval) determines the sampling rate of the input. The default value is 1. 
+* sampling ii: flag "[-ii <sampling II>]". The ii (initiation interval) determines the sampling rate of the input. The default value is 1. 
 
 
 Profiling