legaldb renamed from caselaw

Author: TimidRobot

content/blog/authors/krysal/contents.lr

@@ -5,4 +5,4 @@ name: Krystle Salazar
 md5_hashed_email: f36bcb2678c0c0845f8adf634c4d764b
 ---
 about:
-Krystle is a Software Developer from Venezuela, working on **Reimplement [CC’s Legal Database](https://github.com/creativecommons/caselaw) using Django** as part of Outreachy Summer round of 2020. You can find her as `@krysal` on the CC Slack.
+Krystle is a Software Developer from Venezuela, working on **Reimplement [CC’s Legal Database](https://github.com/creativecommons/legaldb) using Django** as part of Outreachy Summer round of 2020. You can find her as `@krysal` on the CC Slack.

content/blog/entries/legal-database-a-new-beginning/contents.lr

@@ -53,10 +53,10 @@ It has only been a week so we're just starting, so next task to do sooner are:
 ### How you can help
 
 We are still discussing the new image before start coding so these are some options if you want to get involved:
-- Suggest improvements to designs/UX or new features joining the discussion on the [`#cc-dev-legal-database`](https://creativecommons.slack.com/channels/cc-dev-legal-database) Slack channel or on the [github](https://github.com/creativecommons/caselaw) project.
+- Suggest improvements to designs/UX or new features joining the discussion on the [`#cc-dev-legal-database`](https://creativecommons.slack.com/channels/cc-dev-legal-database) Slack channel or on the [github](https://github.com/creativecommons/legaldb) project.
 - Contribute directly to the CC's Vocabulary design system on [github](https://github.com/creativecommons/vocabulary).
 - Submit a case or a scholarship related to CC licenses on the [current site](https://labs.creativecommons.org/caselaw/contribute/).
 
 **CC Legal Database** is my Outreachy project for this summer, under the guidance of Director of Engineering [Kriti Godey](https://creativecommons.org/author/kriticreativecommons-org/) and Core Systems Manager [Timid Robot Zehta](https://creativecommons.org/author/timidcreativecommons-org/), they are very supportive and the CC community is notable welcoming.
 
-This is the first post of a series so stay tuned if you're interested to know more.
+This is the first post of a series so stay tuned if you're interested to know more.

content/blog/entries/legal-database-features/contents.lr

@@ -39,7 +39,7 @@ While developing the mentioned functionalities I was also in charge of adding au
     <figcaption>Example of page obtained when requesting a case detail that is not published or doesn't exist.</figcaption>
 </figure>
 
-In this process of adding automated tests I wanted them to run on every pull request created, so I learned how to write a GitHub Action with a PostgreSQL service, the DBMS used in this case. Previously, I had already created a job for linting, so I needed to add another one to run in parallel to save time. This service provided by GitHub is pretty cool and useful, it opens up a world of possibilities, from running third party services like [Lighthouse test](https://github.com/GoogleChrome/lighthouse-ci) to even [send tweets](https://github.com/gr2m/twitter-together)! If you want to see the GitHub Action file configurated for this project, check it out: [`.github/workflows/main.yml`](https://github.com/creativecommons/caselaw/blob/31c3002a7860d78f3fdb464150c5c1b2f8bb86fc/.github/workflows/main.yml).
+In this process of adding automated tests I wanted them to run on every pull request created, so I learned how to write a GitHub Action with a PostgreSQL service, the DBMS used in this case. Previously, I had already created a job for linting, so I needed to add another one to run in parallel to save time. This service provided by GitHub is pretty cool and useful, it opens up a world of possibilities, from running third party services like [Lighthouse test](https://github.com/GoogleChrome/lighthouse-ci) to even [send tweets](https://github.com/gr2m/twitter-together)! If you want to see the GitHub Action file configurated for this project, check it out: [`.github/workflows/main.yml`](https://github.com/creativecommons/legaldb/blob/31c3002a7860d78f3fdb464150c5c1b2f8bb86fc/.github/workflows/main.yml).
 
 ### Accessibility
 
@@ -67,4 +67,4 @@ Some other features were implemented but only relevant to our registered users,
 
 After reviewing all done this last month I see significant progress has been made, I have learned many things along the way: more of what Django and its ecosystem offers, about accessibility, continuous integration in Heroku and GitHub, and more. One of the things that makes me most happy is being able to be contributing and being part of an Open Source organization, knowing how it moves and works inside, something I never imagine before.
 
-Time flies and there are less than two weeks left to finish, so if you want to follow the project here is the repository to suggest improvements or report bugs, or if you prefer something less technical you can join us on the [slack channel](https://creativecommons.slack.com/channels/cc-dev-legal-database).
+Time flies and there are less than two weeks left to finish, so if you want to follow the project here is the repository to suggest improvements or report bugs, or if you prefer something less technical you can join us on the [slack channel](https://creativecommons.slack.com/channels/cc-dev-legal-database).

content/community/contents.lr

@@ -42,8 +42,8 @@ The channels most relevant to CC's developer community are:
       <td><a href="https://github.com/creativecommons/cccatalog-dataviz">CC Catalog visualizations.</a></td>
     </tr>
     <tr>
-      <td><code>#cc-dev-legal-database</code></td>
-      <td><a href="https://labs.creativecommons.org/caselaw/">CC Legal Database.</a></td>
+      <td><code>#cc-dev-legaldb</code></td>
+      <td><a href="https://github.com/creativecommons/legaldb">CC Legal Database.</a></td>
     </tr>
     <tr>
       <td><code>#cc-dev-license-chooser</code></td>