fix links

docs/project-team/project-guidelines/part4-product-spec-learning-phase.md

@@ -14,7 +14,7 @@ This is an **extremely important phase of your project that should not be taken
 
 **We do NOT encourage beginning project development until the entire spec has been completed, presented, and approved.** This is in order to provide your team with useful feedback and to help your team identify any potential gaps in your research or design for your team to fill in.
 
-Here’s the **[Google Docs template](https://hcp-uw.github.io/docs/project-team/resources/product-spec-template)** to get started. You can also navigate to `Resources/Project Spec Template` on this documentation website to find the spec template. This document highlights the requirements you need to meet with your technical spec and also has a template guide to follow. Please reference it closely and ask club leadership if you have any questions.
+Here’s the **[Google Docs template](https://docs.google.com/document/d/1q9trXkLShXKabYpFxLDtPcdL_WYOwwfW/edit?usp=sharing&ouid=104753064155446271905&rtpof=true&sd=true)** to get started. You can also navigate to `Resources/Project Spec Template` on this documentation website to find the spec template. This document highlights the requirements you need to meet with your technical spec and also has a template guide to follow. Please reference it closely and ask club leadership if you have any questions.
 
 Refer to your designated club lead guide for example specs to read. When you finish a rough draft of your spec, feel free to ask your club lead guide to give it a read-through and provide some feedback! We’re always happy to help and provide support to our project teams. **Once your team is done with your spec**, there will be a spec presentation day where your team will present your spec and get feedback on! Go to **Part 5** to see how this will work.
 
@@ -24,7 +24,7 @@ Refer to your designated club lead guide for example specs to read. When you fin
 
 In order to optimize your time with your project, we recommend that you begin exploring the technologies associated with building your product while you are designing. However, don’t go too far into the deep end just in case you might have to switch programming languages. Do some general learning projects with your teammates so that you learn together! But, if your team is sure about which stack they will use, then get started with your learning phase ASAP.
 
-There is no exact order where the learning phase fits into this timeline, but we recommend that you should begin when your team has begun writing their spec and knows what tech stack they plan to use. But the sooner, the better. Here’s a **[list of resources](https://docs.google.com/spreadsheets/d/1S7ma9SIpmoV406har6Ur3AlmY-1kOnJNpcQsGjITu3w/edit#gid=0)** that may cover the languages/technologies you plan to use. If it's not here and you're having trouble finding the resources yourself, contact your project guide for support!
+There is no exact order where the learning phase fits into this timeline, but we recommend that you should begin when your team has begun writing their spec and knows what tech stack they plan to use. But the sooner, the better. If it's not here and you're having trouble finding the resources yourself, contact your project guide for support!
 
 ---
 
@@ -34,4 +34,4 @@ The following are links to some great examples of project specs. Feel free to us
 
 - [AlgoViz](https://docs.google.com/document/d/1aPI6hMQnUmd4xSB1iHznqPPwf6O-75pQ/edit?usp=sharing&ouid=110339665080062140802&rtpof=true&sd=true)
 - [Syntext](https://docs.google.com/document/d/1nocWKKrvc7k4Md05yd3QKPVLG9CObYTt/edit?usp=sharing&ouid=110339665080062140802&rtpof=true&sd=true)
-- [UW BeReal](https://docs.google.com/document/d/1KfsGkbPJdpqmdq-rVXRLRTjEGFZ4OJTN/edit?usp=sharing&ouid=110339665080062140802&rtpof=true&sd=true)
+- [UW BeReal](https://docs.google.com/document/d/1KfsGkbPJdpqmdq-rVXRLRTjEGFZ4OJTN/edit?usp=sharing&ouid=110339665080062140802&rtpof=true&sd=true)