Updated review comments

Author: jasminefrancisca

dspic33e-i2c-eeprom/README.md

@@ -10,23 +10,23 @@ then read back using I2C peripheral.
 I2C EEPROM driver module takes two inputs viz., Command and Data Object
 Driver supports two commands viz., Read and Write 
 
-// EEPROM DRIVER Module<br/>
-typedef struct { <br/>
-	unsigned int	cmd; 		// Command Input<br/>
-	I2CEMEM_DATA	*oData;	       	// I2C Serial EEPROM Data Object<br/>
+// EEPROM DRIVER Module  
+typedef struct {   
+	unsigned int	cmd; 		// Command Input  
+	I2CEMEM_DATA	*oData;	       	// I2C Serial EEPROM Data Object  
 	void (*init)(void *);               
-    void (*tick)(void *); <br/>
-    }I2CEMEM_DRV; <br/>
+    void (*tick)(void *);   
+    }I2CEMEM_DRV;   
 
 I2C Serial EEPROM data object contains EEPROM address location, data buffer, size
-of the data buffer and chip select bits for device addressing<br/>
-// Data Object<br/>
-typedef struct { <br/>
-        unsigned int *buff;     	// Data Buffer <br/>
-        unsigned int n;        		// Size of the Data Buffer<br/>
-        unsigned int addr;       	// EEPROM Address<br/>
-        unsigned int csel;            	// Chip Select bits (A2,A1,A0 bits)<br/>
-}I2CEMEM_DATA; <br/>
+of the data buffer and chip select bits for device addressing  
+// Data Object  
+typedef struct {   
+        unsigned int *buff;     	// Data Buffer   
+        unsigned int n;        		// Size of the Data Buffer  
+        unsigned int addr;       	// EEPROM Address  
+        unsigned int csel;            	// Chip Select bits (A2,A1,A0 bits)  
+}I2CEMEM_DATA;   
 
 
 * I2C Serial EEPROM read/write operation begins with transmitting control byte first. 
@@ -43,8 +43,8 @@ Small memory I2C EEPROM will use 1byte address and large memory I2C EEPROM will
 User must select either 1byte memory address or 2byte memory address using 
 i2cEmem.h file. 
 
-// EEPROM ADDRESS SIZE<br/>
-#define ADDRWIDTH   TWO_BYTE    <br/>
+// EEPROM ADDRESS SIZE  
+#define ADDRWIDTH   TWO_BYTE      
 
 
 ## Hardware Used

dspic33e-intr-in-aux-flash/README.md

@@ -6,9 +6,9 @@
 
 This example demonstrates how to handle interrupts in auxiliary flash. Timer1 interrupt is used to demonstrate this.
 
-aux_int.s 	- 	contains the default ISR for all interrupts in Aux flash <br/>
-init_timer1.c	-	initialise timer 1 interrupt<br/>
-main.c		-	contains main and ISR for timer 1<br/>
+aux_int.s 	- 	contains the default ISR for all interrupts in Aux flash   
+init_timer1.c	-	initialise timer 1 interrupt  
+main.c		-	contains main and ISR for timer 1  
 
 To use this example in your project, include the aux_int.s file.
 

dspic33e-rtcc/README.md

@@ -7,16 +7,16 @@
 This code example aims to demonstrate the basic initialisation and operation of the Real Time Clock and Calender (RTCC) module.
 The user has to ensure the presence of a 32.768kHz secondary oscillator for the module to function as desired.
 
-void RTCCUnlock(void)<br/>
+void RTCCUnlock(void)  
 This function enables the time and date value registers to be written
 
-void RtccInit(void)<br/>
+void RtccInit(void)  
 This function initialises the time and date registers to the user defined values
 
-void RtccRead(void)<br/>
+void RtccRead(void)  
 This function enables the time and date registers to be read
 
-void \_\_attribute\_\_((interrupt, no_auto_psv)) _RTCCInterrupt(void)<br/>
+void \_\_attribute\_\_((interrupt, no_auto_psv)) _RTCCInterrupt(void)  
 This is the Interrupt Service Routine of the RTCC module
 
 User selected bit fields:

dspic33e-rtdm-example/README.md

@@ -9,26 +9,26 @@ alternative link between Host PC and target device for debugging applications
 in real-time using MPLAB DMCI ( MPLAB 8.10 or higher).  
 It is required to include the RTDM.C file and RTDM.h into the application project 
 in order to send/receive data through the UART to/from the host PC running under 
-MPLAB DMCI environment.  <br/><br/>
+MPLAB DMCI environment.      
 DMCI included in MPLAB 8.10 or higher is ready and enabled to support data exchange 
 between the host PC and target device. Previous versions of DMCI do not support this feature. 
 RTDM is currently supported by PIC24H, dsPIC30F , dsPIC33F , PIC24E and dsPIC33E processors
 
 
-Function: RTDM_Start()<br/>
+Function: RTDM_Start()  
 Overview: Here is where the RTDM code initializes the UART to be used to
-		  exchange data with the host PC<br/>
+		  exchange data with the host PC  
 Note:	  Some processors may have 2 UART modules, that is why it is required to
 		  specify which UART module is going to be used by RTDM	
 
 
-Function: RTDM_ProcessMsgs()<br/>
+Function: RTDM_ProcessMsgs()  
 Overview: Here is where the RTDM code process the message received and then 
 		  executes the required task. These tasks are reading an specified memory
 		  location, writing an specified memory location, receive a communication
 		  link sanity check command, or being asked for the size of the buffers.
 
-Function: CloseRTDM()<br/>
+Function: CloseRTDM()  
 Overview: Here is where the RTDM code closes the UART used to
 		  exchange data with the host PC
 

dspic33e-rtsp-word-write/README.md

@@ -10,9 +10,9 @@ in the already programmed flash are modified and read back to verify the modific
 
 Following RTSP Application Program Interface (APIs) are used to perform the operation.
 
-// Flash Memory is organised into ROWs of 64 instructions or 192 bytes<br/>
-// RTSP allows the user to erase a PAGE of memory which consists of EIGHT ROWs (512 instructions or 1536byts) at a time.<br/>
-// RTSP allows the user to program a ROW (64 instructions or 192 bytes) at a time<br/>
+// Flash Memory is organised into ROWs of 64 instructions or 192 bytes  
+// RTSP allows the user to erase a PAGE of memory which consists of EIGHT ROWs (512 instructions or 1536byts) at a time.  
+// RTSP allows the user to program a ROW (64 instructions or 192 bytes) at a time  
 
 ## Hardware Used