EpicGamesExt -> EpicGames

README.md

@@ -5,7 +5,7 @@ debugger itself, and is intended as a technical overview of the project. The
 debugger's README, which includes usage instructions and tips, can be found
 packaged along with debugger releases, or within the `build` folder after a
 local copy has been built. You can find pre-built release binaries
-[here](https://github.com/EpicGamesExt/raddebugger/releases)._
+[here](https://github.com/EpicGames/raddebugger/releases)._
 
 The RAD Debugger is a native, user-mode, multi-process, graphical debugger. It
 currently only supports local-machine Windows x64 debugging with PDBs, with
@@ -14,7 +14,7 @@ support native Linux debugging and DWARF debug info.
 
 The debugger is currently in *ALPHA*. In order to get the debugger
 bullet-proof, it'd greatly help out if you submitted the issues you find
-[here](https://github.com/EpicGamesExt/raddebugger/issues), along with any
+[here](https://github.com/EpicGames/raddebugger/issues), along with any
 information you can gather, like dump files (along with the build you used),
 instructions to reproduce, test executables, and so on.
 

src/base/base_context_cracking.h

@@ -187,7 +187,7 @@
 #endif
 
 #if !defined(BUILD_ISSUES_LINK_STRING_LITERAL)
-# define BUILD_ISSUES_LINK_STRING_LITERAL "https://github.com/EpicGamesExt/raddebugger/issues"
+# define BUILD_ISSUES_LINK_STRING_LITERAL "https://github.com/EpicGames/raddebugger/issues"
 #endif
 
 #define BUILD_TITLE_STRING_LITERAL BUILD_TITLE " (" BUILD_VERSION_STRING_LITERAL " " BUILD_RELEASE_PHASE_STRING_LITERAL ") - " __DATE__ "" BUILD_GIT_HASH_STRING_LITERAL_APPEND BUILD_MODE_STRING_LITERAL_APPEND

src/raddbg/raddbg.mdesk

@@ -2522,7 +2522,7 @@ raddbg_readme:
   
   @p "**Configuration files (users and projects):** The RAD Debugger stores configuration in two files. One is the 'user file', the other is the 'project file'. Both files are the same format and can store the same kinds of data, but the user file is preferred by the debugger for more likely user-related data (windows, keybindings, theme), and the project file is preferred by the debugger for more likely project-related data (executable debugging targets, breakpoints, recent source files). Project files are more likely to be what you'd check into source control, whereas a user file is more likely to have your personal debugger settings (which will apply identically regardless of which project file is opened).";
   
-  @p "The debugger autosaves user and project files. You do not need to manually save them. To switch which path you are using for either, you can use the `Open User` (Ctrl + Alt + Shift + O, by default), or `Open Project` (Ctrl + Alt + O, by default) commands respectively. If a file does not exist at the path you enter for either, then a new one will be created, and the debugger will begin autosaving to it. If the initial paths to these files are not specified on the command line (via `--user` or `--project`), then the debugger uses default paths for them. The user file path, by default, will be `%appdata%/raddbg/default.raddbg_user`. The project file path will be whatever project path was last loaded for the user, or if no such path exists, `%appdata%/raddbg/default.raddbg_project`. If you suspect that your configuration files are corrupted or causing the debugger to behave poorly, it might help to delete your `%appdata%/raddbg` folder (although it'd also help if you [sent it to us in a bug report](https://github.com/EpicGamesExt/raddebugger/issues), so that we can investigate why they were corrupted to begin with!).";
+  @p "The debugger autosaves user and project files. You do not need to manually save them. To switch which path you are using for either, you can use the `Open User` (Ctrl + Alt + Shift + O, by default), or `Open Project` (Ctrl + Alt + O, by default) commands respectively. If a file does not exist at the path you enter for either, then a new one will be created, and the debugger will begin autosaving to it. If the initial paths to these files are not specified on the command line (via `--user` or `--project`), then the debugger uses default paths for them. The user file path, by default, will be `%appdata%/raddbg/default.raddbg_user`. The project file path will be whatever project path was last loaded for the user, or if no such path exists, `%appdata%/raddbg/default.raddbg_project`. If you suspect that your configuration files are corrupted or causing the debugger to behave poorly, it might help to delete your `%appdata%/raddbg` folder (although it'd also help if you [sent it to us in a bug report](https://github.com/EpicGames/raddebugger/issues), so that we can investigate why they were corrupted to begin with!).";
   @p "For more information, see the `**User & Project Files** section.";
   
   @p "**Watch tabs and visualizers:** 'Watch' tabs in the RAD Debugger allow entering expressions, which can reference variables in your program, and visualize what their value is when your program is stopped at a particular time. These expressions roughly follow C expression syntax, but there are a number of extensions which can be used to visualize expressions in a more useful way. Here are some examples:";

src/raddbg/raddbg_core.c

@@ -7197,7 +7197,7 @@ rd_window_frame(void)
                     UI_Row UI_Padding(ui_pct(1, 0)) UI_TextAlignment(UI_TextAlign_Center) UI_PrefWidth(ui_text_dim(ui_top_font_size()*2.f, 1))
                     UI_CornerRadius(ui_top_font_size()*0.5f)
                   {
-                    String8 url = str8_lit("https://github.com/EpicGamesExt/raddebugger/issues");
+                    String8 url = str8_lit("https://github.com/EpicGames/raddebugger/issues");
                     UI_Signal sig = ui_button(str8_lit("Submit request, issue, or bug report"));
                     if(ui_clicked(sig))
                     {
@@ -7655,7 +7655,7 @@ rd_window_frame(void)
           ui_box_equip_display_fstrs(label, &fstrs);
           if(ui_clicked(sig))
           {
-            wm_open_in_browser(s("https://github.com/EpicGamesExt/raddebugger/releases/latest"));
+            wm_open_in_browser(s("https://github.com/EpicGames/raddebugger/releases/latest"));
           }
         }
         
@@ -12841,7 +12841,7 @@ rd_frame(void)
         {
           .id = 1,
           .method = HTTP_Method_Get,
-          .url = s("https://api.github.com/repos/EpicGamesExt/raddebugger/releases/latest"),
+          .url = s("https://api.github.com/repos/EpicGames/raddebugger/releases/latest"),
           .user_agent = s("raddebugger"),
         };
         http_push_request(rd_state->update_check_http_ring, &p, 0);