Convert Docs to Consistent Naming Scheme

In #48 we discussed that the documentation files did not have
a very consistent naming scheme. Some were using "_", "-", or " ".

This commit converts them to one consistent style.

Author: stwrt

docs/Build & Debug/DebuggingWithXcode.md

@@ -5,8 +5,8 @@ You can use Xcode to build & debug WebKit. Open `WebKit.xcworkspace` at the top
 In order to make Xcode use build files built by `make` command above,
 go to File > Workspace Settings... > Advanced... > Custom > Relative to Workspace
 and adjust the relative paths of Products and Intermediates to point to `WebKitBuild` directory.
-![Screenshot of Xcode Workspace Settings](../assets/xcode-workspace-settings.png)
-![Screenshot of Xcode Workspace Settings - Advanced Build Location](../assets/xcode-workspace-build-location.png)
+![Screenshot of Xcode Workspace Settings](/assets/XcodeWorkspaceSettings.png)
+![Screenshot of Xcode Workspace Settings - Advanced Build Location](/assets/XcodeWorkspaceBuildLocation.png)
 Note that debugging WebCore code typically requires attaching to the relevant WebContent process,
 not the application process, which is mostly running code in [Source/WebKit/UIProcess](https://github.com/WebKit/WebKit/tree/main/Source/WebKit/UIProcess).
 Depending on what you’re debugging, you’d have to attach & debug different processes in the coalition.
@@ -35,10 +35,10 @@ In Product > Scheme, select “All Source”.
 In Product > Scheme > Edit Scheme, open “Run” tab.
 Pick WebKitTestRunner or DumpRenderTree, whichever is desired in “Executable”.
 
-![Screenshot of specifying DumpRenderTree as the target of "Run" scheme](../assets/xcode-scheme-dumprendertree.png)
+![Screenshot of specifying DumpRenderTree as the target of "Run" scheme](/assets/XcodeSchemeDumpRenderTree.png)
 Go to Arguments and specify the path to the layout tests being debugged relative to where the build directory is located.
 e.g. `../../LayoutTests/fast/dom/Element/element-traversal.html` if `WebKitBuild/Debug` is the build directory.
-![Screenshot of Xcode specifying a layout test in an argument to DumpRenderTree](../assets/xcode-scheme-layout-test.png)
+![Screenshot of Xcode specifying a layout test in an argument to DumpRenderTree](/assets/XcodeSchemeLayoutTest.png)
 You may want to specify OS_ACTIVITY_MODE environmental variable to “disable”
 in order to suppress all the system logging that happens during the debugging session.
 
@@ -49,7 +49,7 @@ Once this is done, you can run WebKitTestRunner or DumpRenderTree by going to Pr
 
 Clicking on “Run” button may be significantly slower due to Xcode re-building every project and framework each time.
 You can disable this behavior by going to “Build” tab and unchecking boxes for all the frameworks involved for “Run”:
-![Screenshot of Xcode unchecking build options for all but DumpRenderTree for "Run" scheme](../assets/xcode-build-settings-for-run.png)
+![Screenshot of Xcode unchecking build options for all but DumpRenderTree for "Run" scheme](/assets/XcodeBuildSettingsForRun.png)
 
 ### Attaching to WebContent Process
 

docs/Deep Dive/Architecture/JSWrappers.md

@@ -32,7 +32,7 @@ Each `DOMWrapperWorld` has its own JS wrapper for each C++ object.
 As a result, a single C++ object may have multiple JS wrappers in distinct `DOMWrapperWorld`s.
 The most important `DOMWrapperWorld` is the main `DOMWrapperWorld` which runs the scripts of web pages WebKit loaded
 while other `DOMWrapperWorld`s are typically used to run code for browser extensions and other code injected by applications that embed WebKit.
-![Diagram of JS wrappers](../../assets/js-wrapper.png)
+![Diagram of JS wrappers](/assets/JSWrapper.png)
 JSX.h provides `toJS` functions which creates a JS wrapper for X
 in a given [global object](https://developer.mozilla.org/en-US/docs/Glossary/Global_object)’s `DOMWrapperWorld`,
 and toWrapped function which returns the underlying C++ object.

docs/Deep Dive/Architecture/Storage.md

@@ -19,7 +19,7 @@ StorageAreaBases)
 * MemoryStorageArea / SQLiteStorageArea (inherits StorageAreaBases; manage one local or session storage, like
 Webkit::StorageArea)
 
-![Storage Manager](../../assets/Storage%20Manager.svg)
+![Storage Manager](/assets/StorageManager.svg)
 
 
 ### Notes

docs/Deep Dive/Architecture/WebKit2.md

@@ -13,7 +13,7 @@ In addition to handling all network accesses,
 this process is also responsible for managing the disk cache and Web APIs that allow websites
 to store structured data such as [Web Storage API](https://developer.mozilla.org/en-US/docs/Web/API/Web_Storage_API)
 and [IndexedDB API](https://developer.mozilla.org/en-US/docs/Web/API/IndexedDB_API):
-![Diagram of WebKit2's multi-process architecture](../../assets/webkit2-process-architecture.png)
+![Diagram of WebKit2's multi-process architecture](/assets/Webkit2ProcessArchitecture.png)
 Because a WebContent process can Just-in-Time compile arbitrary JavaScript code loaded from the internet,
 meaning that it can write to memory that gets executed, this process is tightly sandboxed.
 It does not have access to any file system unless the user grants an access,

docs/Deep Dive/Build/AddingNewFile.md

@@ -11,12 +11,12 @@ Make sure to uncheck the target membership so that it’s not compiled as a part
 Instead, add the same file in Sources.txt file that exists in each subdirectory of Source.
 e.g. [Source/WebCore/Sources.txt](https://github.com/WebKit/WebKit/blob/main/Source/WebCore/Sources.txt) for WebCore.
 This will ensure the newly added file is compiled as a part of *unified sources*.
-![Screenshot of adding a file to Xcode](../../assets/xcode-add-file.png)
+![Screenshot of adding a file to Xcode](/assets/XcodeAddFile.png)
 When a header file in WTF is used in WebCore, or a header file in WebCore is used in WebKit or WebKitLegacy,
 we need to export the file to those projects.
 To do that, turn on the target membership in respective framework as set the membership to “Private” as seen below.
 This will ensure the relevant header file is exported from WTF / WebCore to other downstream projects like WebKitLegacy.
-![Screenshot of exporting a header file](../../assets/xcode-export-header.png)
+![Screenshot of exporting a header file](/assets/XcodeExportHeader.png)
 
 Non-cocoa ports, like WPE and GTK, use CMake for building the project. If the header is not platform-specific, you might 
 want to add an entry for it into the relevant Headers.cmake. For example, if a WebCore header is included by WebKit, you