Deliverable-3/Final-Document/Challenges-and-How-We-Solved-Them.md

@@ -29,15 +29,15 @@ Issue: Navigating to the inventory screen created multiple stacked instances, re
 Root Cause: Improper navigation handling and lack of data refresh upon return.  
 Solution: Used navigation.goBack() combined with useFocusEffect to refresh inventory data automatically upon returning.  
 Outcome: Navigation streamlined; inventory updates instantly after item changes.                     
-**6. Api Integration**
-Issue: Integrating the API and displaying data that was both relevant and necessary to the user experience
-Root Cause: The root cause of the issue was with the api especially pertaining to image quality and also recipe information. For example the images when taken from the Api request were always blurry and did not look very good.
-Solution: Rather than making the images bigger I scaled them down on the screen and used things in the styling such as image: 'contain' which made the images look better but only to a certain extent.
+**6. Api Integration**  
+Issue: Integrating the API and displaying data that was both relevant and necessary to the user experience.  
+Root Cause: The root cause of the issue was with the api especially pertaining to image quality and also recipe information. For example the images when taken from the Api request were always blurry and did not look very good.  
+Solution: Rather than making the images bigger I scaled them down on the screen and used things in the styling such as image: 'contain' which made the images look better but only to a certain extent.  
 **7. Food Log**  
 Issue: Updating user calories correctly so that the calorie tracker page can track the calories and display them.  
 Root Cause: The root cause of this problem was that the update was being called wrong and instead of updating it was never sent.  
 Solution: rather than using the updateUser with userId and calories being passed, instead updateUserCalories was the correct way to update the calories.  
 **8. Expense Tracker**  
 Issue: Displaying variables within the pie chart and page without conflicting with the async and accessing variables before their values are updated.  
-Root Cause: The root cause of this problem was that the variables would causes unexpected problems
-Solution: Creating local variables within the async function to access values and also creating a loading screen so that the the async function would finish before displaying the on the screen.
+Root Cause: The root cause of this problem was that the variables would causes unexpected interactions.  
+Solution: Creating local variables within the async function to access values and also creating a loading screen so that the the async function would finish before displaying the on the screen.  
\ No newline at end of file