updated toc tree and naming (#2338)

SpecFlowOSS · Mar 3, 2021 · 97a5ec2 · 97a5ec2
1 parent 992065c
commit 97a5ec2
Show file tree

Hide file tree

Showing 8 changed files with 10 additions and 12 deletions.
diff --git a/docs/Rider/rider-features.md b/docs/Rider/rider-features.md
@@ -1,4 +1,4 @@
-# Rider features
+# Features
 
 The SpecFlow for Rider plugin is bundled with a handful of features, see below for more details.
 
@@ -14,11 +14,11 @@ There are multiple ways to achieve this:
 
 ![Rider_nav2](../_static/images/rider_nav2.gif)
 
-3- To navigate from a binding to its corresponding Gherkin step, the keyboard shortcuts **(Shift + F12)** can be used :
+2- To navigate from a binding to its corresponding Gherkin step, the keyboard shortcuts **(Shift + F12)** can be used :
 
 ![Rider_nav3](../_static/images/rider_nav3.gif)
 
-4- You can also see all Gherkin steps currently using a particular binding by pressing **F12** or by navigating to it ***Go to ➡ Go to Declarations or Usages*** :
+3- You can also see all Gherkin steps currently using a particular binding by pressing **F12** or by navigating to it ***Go to ➡ Go to Declarations or Usages*** :
 
 ![Rider_nav4](../_static/images/rider_nav4.gif)
 

diff --git a/docs/Rider/rider-installation.md b/docs/Rider/rider-installation.md
@@ -1,6 +1,4 @@
-# Rider Installation
-
-## Installation
+# Installation
 
 The SpecFlow for Rider plugin can be found either at the [JetBrains marketplace](https://plugins.jetbrains.com/plugin/15957-specflow-support) or directly from within the Rider IDE.
 

diff --git a/docs/visualstudio/Generating-Skeleton-Code.md b/docs/visualstudio/Generating-Skeleton-Code.md
@@ -1,4 +1,4 @@
-# Visual Studio Generating Skeleton Code
+# Generating Skeleton Code
 
 You can automatically create a suitable class with skeleton bindings and methods in Visual Studio. To do so:
 

diff --git a/docs/visualstudio/Visual-Studio-Integration-Editing-Features.md b/docs/visualstudio/Visual-Studio-Integration-Editing-Features.md
@@ -1,4 +1,4 @@
-# Visual Studio Editing Features
+# Editing Features
 
 The Visual Studio integration includes the following features to make it easier to edit feature files and identify which steps have already been bound.
 

diff --git a/docs/visualstudio/Visual-Studio-Integration-Navigation-Features.md b/docs/visualstudio/Visual-Studio-Integration-Navigation-Features.md
@@ -1,4 +1,4 @@
-# Visual Studio Navigation Features
+# Navigation Features
 
 You can navigate between the methods in your bindings and the associated steps in your Gherkin feature files. 
 

diff --git a/docs/visualstudio/Visual-Studio-Integration.md b/docs/visualstudio/Visual-Studio-Integration.md
@@ -1,4 +1,4 @@
-# Visual Studio Integration
+# Integration
 
 The Visual Studio integration includes a number of features that make it easier to edit Gherkin files and navigate to and from bindings in Visual Studio. You can also generate skeleton code including step definition methods from feature files. The Visual Studio integration also allows you to execute tests from Visual Studio's Test Explorer.
 

diff --git a/docs/visualstudio/Visual-Studio-Test-Explorer-Support.md b/docs/visualstudio/Visual-Studio-Test-Explorer-Support.md
@@ -1,4 +1,4 @@
-# Visual Studio Test Explorer Support
+# Test Explorer Support
 
 The Visual Studio integration supports executing SpecFlow scenarios from the Visual Studio Test Explorer. The basic Test Explorer features work with all unit test providers, although you may need to install additional Visual Studio connectors, depending on the unit test framework. Full integration is provided for [SpecFlow+ Runner](https://specflow.org/plus/runner/), meaning you can run and debug your scenarios as first class citizens:
 

diff --git a/docs/visualstudio/visual-studio-installation.md b/docs/visualstudio/visual-studio-installation.md
@@ -1,4 +1,4 @@
-# Visual Studio Installation
+# Installation
 
 The integration packages can also be downloaded and installed separately from the Visual Studio Gallery: