Skip to content

Commit c207885

Browse files
committed
Fix some Markdown formatting issues in the README.
1 parent 795b1d4 commit c207885

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

README.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -3,19 +3,19 @@
33
A basic MIT licensed Mercurial source control plugin for Unreal Engine 4.
44

55
##Overview
6-
-------------
6+
77
The Unreal Editor has built-in visual diffing for Blueprint assets, this feature relies on a **Source Control Provider** plugin to interface with the repository your assets are stored in. Currently UE4 ships with built-in source control provider plugins for SVN and Perforce. This source control provider plugin allows the Unreal Editor to interact with a Mercurial repository, thus unlocking all the built-in asset diffing goodness for those of us who prefer to use Mercurial.
88

99
##Supported Operating Systems
10-
----------------------------------
10+
1111
The plugin should work on any OS the Unreal Editor can run on, however, I do all my development on Windows so if something isn't working right on another OS please let me know how to fix it :).
1212

1313
##Branches
14-
----------
14+
1515
The **master** branch should be compatible with the latest binary release of UE4, I will be creating another branch to stay up to date with the **UE4 master** branch.
1616

1717
##Installation
18-
------------
18+
1919
###Prerequisites
2020
You need Mercurial installed on your system, preferably a standalone version that doesn't rely on Python (though that may work too, I just haven't tried). On Windows I'd recommend installing [TortoiseHg](http://tortoisehg.bitbucket.org/), the plugin will then auto-detect the location of the relevant Mercurial executable.
2121

@@ -49,7 +49,7 @@ Then follow these steps on Windows (adjust as needed on other OSes):
4949
2. Open the generated Visual Studio solution file (e.g. **MyProject.sln**) and build it.
5050
3. Launch the Unreal Editor, open the project you've just built, and follow the instructions in the next section.
5151

52-
*Note that your existing project must have a **Source** subdirectory with a couple of **.Target.cs** files in it, if it doesn't you may need to follow the steps in the **Building from Scratch** section below and then copy the built plugin into your project(s).*
52+
Note that your existing project must have a **Source** subdirectory with a couple of **.Target.cs** files in it, if it doesn't you may need to follow the steps in the **Building from Scratch** section below and then copy the built plugin into your project(s).
5353

5454
###Editor Configuration
5555
Once you've got a binary version of the plugin (either by building or downloading) follow these steps:
@@ -62,8 +62,8 @@ Once you've got a binary version of the plugin (either by building or downloadin
6262
6. If you installed [TortoiseHg](http://tortoisehg.bitbucket.org/) the **Mercurial Executable** should've been auto-detected, otherwise you need to specify the location of the Mercurial executable (hg.exe on Windows, may be just hg elsewhere).
6363
7. Press the **Accept Settings** button to enable the Mercurial source control provider.
6464

65-
Building from Scratch
66-
-------------------------
65+
##Building from Scratch
66+
6767
The following steps explain how to build the plugin as part of a new (mostly) empty project, in case you hit any issues while attempting to build it as part of an existing project, or as an engine plugin.
6868

6969
1. Create a new **Basic Code (C++)** project from the UE4 editor, e.g. **MyProject**, close the editor.

0 commit comments

Comments
 (0)