srydell -> Tolc-Software

Done during migration from a user repo to a company repo

README.md

@@ -1,4 +1,4 @@
-![Ubuntu](https://github.com/srydell/Parser/workflows/Ubuntu/badge.svg) ![MacOS](https://github.com/srydell/Parser/workflows/MacOS/badge.svg) ![Windows](https://github.com/srydell/Parser/actions/workflows/windows.yml/badge.svg) ![Windows-debug-deploy](https://github.com/srydell/Parser/actions/workflows/windows-debug-deploy.yml/badge.svg)
+![Ubuntu](https://github.com/Tolc-Software/Parser/workflows/Ubuntu/badge.svg) ![MacOS](https://github.com/Tolc-Software/Parser/workflows/MacOS/badge.svg) ![Windows](https://github.com/Tolc-Software/Parser/actions/workflows/windows.yml/badge.svg) ![Windows-debug-deploy](https://github.com/Tolc-Software/Parser/actions/workflows/windows-debug-deploy.yml/badge.svg)
 
 # Parser #
 

docs/internal/addingContainer.md

@@ -2,7 +2,7 @@
 
 This document describes how to add support for parsing a new type of standard library container (or anything that can contain types).
 
-1. In the [IntermediateRepresentation repo](https://github.com/srydell/IntermediateRepresentation), start by adding an `enum` value to `IR::ContainerType` corresponding to your new container.
+1. In the [IntermediateRepresentation repo](https://github.com/Tolc-Software/IntermediateRepresentation), start by adding an `enum` value to `IR::ContainerType` corresponding to your new container.
 2. Add a test in the root of the `tests` directory. The naming convention is the plural version of the container name. Use another container test as a starting point. For example `lists.cpp`.
 3. Change the `code` block so that the container is used.
 4. Add the test to the `CMakeLists.txt` file in the `tests` directory.