From 1bde32ac0adeb8662027e01bc64a946d60256407 Mon Sep 17 00:00:00 2001
From: kartikmashal8 <67013900+kartikmashal8@users.noreply.github.com>
Date: Thu, 1 Oct 2020 00:50:59 +0530
Subject: [PATCH] Update readme.md

---
 readme.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/readme.md b/readme.md
index bd5c6a1..4c0ae56 100644
--- a/readme.md
+++ b/readme.md
@@ -313,7 +313,7 @@ Because of this rule, you should always pad the `*` type qualifier with spaces.
 But, always declare the name of any pointer argument to communicate if it's a pointer-to-array (plural name) or a pointer-to-value (singular name).
 
 ``` c
-bool trie_eq( Trie trie1, Trie trie2 );         // Bad
+bool trie_eq( Trie trie1, Trie trie2 );         // Bad(Function decleration)
 bool trie_eq( Trie, Trie );                     // Good
 
 // Bad - are these pointers for modification, nullity, or arrays?
@@ -330,7 +330,7 @@ void trie_add( Trie const * trie, char const * string );
 From *21st Century C*, by Ben Klemens:
 
 ``` c
-printf( "%f\n", ( float )333334126.98 );    // 333334112.000000
+printf( "%f\n", ( float )333334126.98 );    // 333334112.000000(Type Casting)
 printf( "%f\n", ( float )333334125.31 );    // 333334112.000000
 ```
 
@@ -354,7 +354,7 @@ I think it's alright to bunch semantically-connected struct members together, th
 
 ``` c
 // Fine
-typedef struct Color {
+typedef struct Color { //Defining Structure
     char r, g, b;
 } Color;
 ```