Updates and added Issue templates

Author: PagelsR

learn-pr/github/manage-innersource-program-github/includes/2-manage-innersource-program.md

@@ -69,6 +69,9 @@ Check out some [Awesome README examples](https://github.com/matiassingers/awesom
 
 Once the project launches, use email and other networking channels to promote it. Reaching an appropriate audience could produce a significant boost in project participation.
 
+[Learn more about README files in the GitHub documentation.](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes)
+
+
 ### Manage projects on GitHub
 
 As projects gain traction, the influx of users and contributions can require lots of work to manage. Depending on the project, a significant amount of work might be required just to manage the expectations of project participants.

learn-pr/github/manage-work-github-projects/includes/3-how-to-create-project.md

@@ -8,7 +8,7 @@ In this unit, you learn how to:
 - Set the name, description, and README of your Project.
 - Add issues and pull requests to your Project.
 
-## Creating an organization-level Project
+## Creating an organization-owned Project
 
 First, you want to lay the foundation by creating a new Project. Creating is relatively quick and simple.
 
@@ -26,7 +26,10 @@ First, you want to lay the foundation by creating a new Project. Creating is rel
 
 You just created a Project!
 
-You can also create a personal Project by selecting your profile photo and navigating to **Your projects**. Once you're on your Projects page, select the green button titled **New project**.
+> [!TIP]
+> You can also create a personal Project by selecting your profile photo and navigating to **Your projects**, then clicking **New project**.  
+> Additionally, Projects can be created directly from a repository—this links the repository to the Project automatically, though the Project itself is still created at the organization level and can be linked to other repositories or projects in the future.
+
 
 ## Set your Project's name, description, and README
 

learn-pr/github/manage-work-github-projects/includes/5-how-to-organize-automate-project.md

@@ -27,18 +27,18 @@ To change your Project's visibility:
 
 ### Manage access to your Project
 
-Access to your Project depends on if your Project is an organization-level Project or a personal/user-level Project. Managing access is similar between the two levels.
+Access to your Project depends on if your Project is an organization-owned Project or a personal/user-owned Project. Managing access is similar between the two levels.
 
-Admins of organization-level Projects can manage access for the entire organization, for teams, for individual organization members, and for outside collaborators. Admins of user-level Projects can invite individual collaborators and manage their access.
+Admins of organization-owned Projects can manage access for the entire organization, for teams, for individual organization members, and for outside collaborators. Admins of user-owned Projects can invite individual collaborators and manage their access.
 
-#### Organization-level Project
+#### Organization-owned Project
 
 - **No access**: Only organization owners and users granted individual access can see the Project. Organization owners are also admins for the Project.
 - **Read**: Everyone in the organization can see the Project. Organization owners are also admins for the Project.
 - **Write**: Everyone in the organization can see and edit the Project. Organization owners are also admins for the Project.
 - **Admin**: Everyone in the organization is an admin for the Project.
 
-#### Personal/User-level Project
+#### Personal/User-owned Project
 
 - **Read**: The individual can view the Project.
 - **Write**: The individual can view and edit the Project.

learn-pr/github/manage-work-github-projects/includes/8-summary.md

@@ -4,7 +4,6 @@ You learned how to:
 
 - Build an organization Project
 - Automate and organize your Project
-- Compare Projects vs Projects (Classic)
 - Use layout options like boards, tables, and timelines
 - Enable default workflows to automate project tasks
 - Convert checklist items into sub-issues for better tracking

learn-pr/github/search-organize-repository-history-github/includes/2-search-organize-repository-history-github.md

@@ -52,7 +52,11 @@ Learn more about [Understanding the search syntax](https://docs.github.com/enter
 
 ## Using Milestones
 
-Milestones let you group issues and pull requests into shared goals, like a sprint, a product release, or a project phase.
+Milestones let you group issues and pull requests into shared goals, like a sprint, a product release, or a project phase. They help teams track progress and keep everyone aligned.
+
+- Milestones can be ordered (just like projects), making it easy to set priorities and visualize which milestones are most important.
+- Progress towards each milestone is tracked automatically—GitHub shows how many issues or PRs are complete and how many remain.
+- Milestones are especially useful for tracking work that goes into separate releases or phases.
 
 ### Create a milestone
 
@@ -68,7 +72,7 @@ Milestones let you group issues and pull requests into shared goals, like a spri
 2. In the right sidebar, select Milestone.
 3. Choose from the list of available milestones.
 
-When you view a milestone, GitHub shows how many issues/PRs are complete and how many remain—making it a helpful planning and tracking tool.
+You can also add milestones as a column to your GitHub Projects layout or display a milestone as a card on a GitHub Projects board. This helps visualize and manage your team’s progress directly from your project planning board.
 
 > You can filter by milestone in GitHub Projects or with advanced search queries like:
 >
@@ -156,6 +160,21 @@ When writing a comment on an issue or pull request, you can insert a saved reply
 
 Saved replies save time and help ensure consistency when responding across your project.
 
+Here’s an updated version that includes guidance on **issue templates**—explaining what they are, how they differ from saved replies, and why they’re usually better for collecting structured information up front.
+
+## Issue Templates
+
+While saved replies are useful for common responses, **issue templates** are a better way to make sure contributors provide all the necessary information when creating new issues.
+
+* **Issue templates** prompt users to fill in specific fields or answer certain questions up front, reducing back-and-forth and ensuring you have the details you need from the start.
+* Templates help maintainers avoid “lost data” by collecting structured information before an issue is even submitted.
+
+**Tip:**
+To set up issue templates, go to your repository’s **Settings** > **Issues** > **Set up templates**. You can create templates for bug reports, feature requests, or anything else your project needs.
+
+> **Best practice:**
+> Use issue templates to capture required details and reduce missing or incomplete information. Use saved replies for routine responses and instructions after issues or pull requests are submitted.
+
 ## Adding assignees
 
 You can assign one or more people to an issue or pull request to show who’s responsible for working on it.