updating content files

content/github/importing-your-projects-to-github/working-with-subversion-on-github/subversion-properties-supported-by-github.md

@@ -8,18 +8,18 @@ versions:
   free-pro-team: '*'
   enterprise-server: '*'
 ---
-### Executable files (svn:executable)
+## Executable files (svn:executable)
 
 We convert `svn:executable` properties by updating the file mode directly before adding it to the Git repository.
 
-### MIME types (svn:mime-type)
+## MIME types (svn:mime-type)
 
 {% data variables.product.product_name %} internally tracks the mime-type properties of files and the commits that added them.
 
-### Ignoring unversioned items (svn:ignore)
+## Ignoring unversioned items (svn:ignore)
 
 If you've set files and directories to be ignored in Subversion, {% data variables.product.product_name %} will track them internally. Files ignored by subversion clients are completely distinct from entries in a *.gitignore* file.
 
-### Currently unsupported properties
+## Currently unsupported properties
 
 {% data variables.product.product_name %} doesn't currently support `svn:externals`, `svn:global-ignores`, or any properties not listed above, including custom properties.

content/github/importing-your-projects-to-github/working-with-subversion-on-github/support-for-subversion-clients.md

@@ -10,9 +10,9 @@ versions:
 ---
 GitHub supports Subversion clients via the HTTPS protocol. We use a Subversion bridge to communicate svn commands to GitHub.
 
-### Supported Subversion features on GitHub
+## Supported Subversion features on GitHub
 
-#### Checkout
+### Checkout
 
 The first thing you'll want to do is a Subversion checkout.  Since Git clones keep the working directory (where you edit files) separate from the repository data, there is only one branch in the working directory at a time.
 
@@ -43,7 +43,7 @@ Subversion checkouts are different: they mix the repository data in the working
   Updated to revision 1.
   ```
 
-#### Creating branches
+### Creating branches
 
 You can also create branches using the Subversion bridge to GitHub.
 
@@ -75,7 +75,7 @@ $ git fetch
 > * [new branch]    more_awesome -> origin/more_awesome
 ```
 
-#### Making commits to Subversion
+### Making commits to Subversion
 
 After you've added some features and fixed some bugs, you'll want to commit those
 changes to GitHub. This works just like the Subversion you're used to. Edit your files, and use `svn commit` to record your changes:
@@ -99,7 +99,7 @@ $ svn commit -m 'Test coverage for problems'
 > Committed revision 4.
 ```
 
-#### Switching between branches
+### Switching between branches
 
 To switch between branches, you'll probably want to start with a checkout of `trunk`:
 
@@ -113,7 +113,7 @@ Then, you can switch to another branch:
 $ svn switch https://github.com/<em>user</em>/<em>repo</em>/branches/more_awesome
 ```
 
-### Finding the Git commit SHA for a Subversion commit
+## Finding the Git commit SHA for a Subversion commit
 
 GitHub's Subversion server exposes the Git commit sha for each Subversion commit.
 
@@ -126,6 +126,6 @@ $ svn propget git-commit --revprop -r HEAD https://github.com/<em>user</em>/<em>
 
 With this commit SHA, you can, for example, look up the corresponding Git commit on GitHub.
 
-### Further reading
+## Further reading
 
 * "[Subversion properties supported by GitHub](/articles/subversion-properties-supported-by-github)"

content/github/importing-your-projects-to-github/working-with-subversion-on-github/what-are-the-differences-between-subversion-and-git.md

@@ -9,7 +9,7 @@ versions:
   free-pro-team: '*'
   enterprise-server: '*'
 ---
-### Directory structure
+## Directory structure
 
 Each *reference*, or labeled snapshot of a commit, in a project is organized within specific subdirectories, such as `trunk`, `branches`, and `tags`. For example, an SVN project with two features under development might look like this:
 
@@ -41,7 +41,7 @@ A Git workflow looks like this:
 
 Unlike SVN, with Git the directory structure remains the same, but the contents of the files change based on your branch.
 
-### Including subprojects
+## Including subprojects
 
 A *subproject* is a project that's developed and managed somewhere outside of your main project. You typically import a subproject to add some functionality to your project without needing to maintain the code yourself. Whenever the subproject is updated, you can synchronize it with your project to ensure that everything is up-to-date.
 
@@ -49,7 +49,7 @@ In SVN, a subproject is called an *SVN external*. In Git, it's called a *Git sub
 
 For more information, see “[Git Tools Submodules](https://git-scm.com/book/en/Git-Tools-Submodules)" in the Git documentation.
 
-### Preserving history
+## Preserving history
 
 SVN is configured to assume that the history of a project never changes. Git allows you to modify previous commits and changes using tools like [`git rebase`](/github/getting-started-with-github/about-git-rebase).
 
@@ -59,7 +59,7 @@ SVN is configured to assume that the history of a project never changes. Git all
 
 {% endtip %}
 
-### Further reading
+## Further reading
 
 - "[Subversion properties supported by GitHub](/articles/subversion-properties-supported-by-github)"
 - ["Branching and Merging" from the _Git SCM_ book](https://git-scm.com/book/en/Git-Branching-Basic-Branching-and-Merging)