Fix typo in title and update Talawa project details

Corrected a typo in the title from 'Introdduction' to 'Introduction' and removed detailed project description for 'Talawa: Emergency Management'.

Author: palisadoes

docs/internships/gsoc-previous/_2026.md

@@ -1,4 +1,4 @@
-## Introdduction
+## Introduction
 
 1. Add ideas at the **_very bottom_** of this document
 2. Use this as an example:
@@ -54,37 +54,6 @@ Preparatory issues may be opened prior to the posting of this ideas page to faci
 
 ---
 
-### Talawa: Emergency Management
-
-1. **Description:** After Hurricane Melissa hit Jamaica, The Palisadoes Foundation was approached to use Talawa to be used in disaster relief efforts. Additional features were required to make it usable. We want to ensure that the app is usable for such situations anywhere in the world by the end of 2026. Talawa was designed to manage the membership of community based organizations. These organizations are often on the forefront of community projects and disaster recovery efforts. We feel that simple project reporting features would be a very useful addition for such organizations in both the web and mobile applications.
-   1. **Field Reporting:** Talawa currently supports attendance at scheduled events with volunteers. However functionality needs to be added to support non-profit organizations supporting relief efforts or regular community projects.
-      1. Types of Reporting: There needs to be a way to report on projects that the organization is working on:
-         1. Project type: Normal or Disaster
-         2. Limited numbers of images and videos of the viscinity
-         3. Audio reports of what is happening, possibly converted to text.
-         4. The option of regular text input
-         5. GeoTags
-         6. The name and contact information of the reporter if available and automatic
-         7. Whether the situation has been resolved or not
-      2. Offline Functionality: In the case of the mobile app, it must be assumed that Internet connectivity may be poor.
-         1. The Field Reporting must be able to operate without access to the API by caching inputted data
-         2. When connectivity is restored, the data must be uploaded automatically to the API with a mechanism to prevent the API from being overloaded from floods of data from recently re-connected geographic areas.
-   2. **Central Reporting:**: There needs to be a project dashboard
-      1. Sortable tabular and geographic map based tagging reports with drill downs
-      2. Ways to request follow up action from the Talawa Admin backend
-1. **Expected Outcomes:** In addition to the outcomes described above, the following must also apply:
-   1. There needs to be ways to identify possible project duplication so that they can be de-duplicated with the original reporters still being updated.
-   2. The solution must assume that the end users have limited literacy skills. The more data points that can be calculated and automated, the better.
-   3. All tests must pass and be valid.
-   4. The overall test code coverage of the repo and individual code files must in all cases be greater than 95%.
-1. **Repos to update:** Talawa-Plugin, Talawa-API, Talawa-Admin
-1. **Skills Required:** Code stacks related to repos above. See introduction section.
-1. **Depends on Project:** None
-1. **Project Size:** 350 hours (Large)
-1. **Possible Mentors:** TBD
-1. **Difficulty:** Hard
-1. **Impact Definition:** "Core development"
-
 ### Talawa Chat Enhancements
 
 1. **Description:** Talawa's chat functionality needs to be expanded for both the mobile and web applications.