From d976df46b2a0e77354a0bd03f0d01ca543caabed Mon Sep 17 00:00:00 2001 From: saideepesh000 Date: Fri, 17 Sep 2021 18:37:49 +0000 Subject: [PATCH] fix(incomplete-sentence): remove incomplete --- versioned_docs/version-5.x/configuring-links.md | 2 +- versioned_docs/version-6.x/configuring-links.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/versioned_docs/version-5.x/configuring-links.md b/versioned_docs/version-5.x/configuring-links.md index ec9ac3c1bb2..884b1270454 100644 --- a/versioned_docs/version-5.x/configuring-links.md +++ b/versioned_docs/version-5.x/configuring-links.md @@ -63,7 +63,7 @@ const state = { }; ``` -By default, React Navigation will use the path segments as the route name when parsing the URL. But directly translating path segments to route names may not be the expected behavior, and your. +By default, React Navigation will use the path segments as the route name when parsing the URL. But directly translating path segments to route names may not be the expected behavior. For example, you might want to parse the path `/feed/latest` to something like: diff --git a/versioned_docs/version-6.x/configuring-links.md b/versioned_docs/version-6.x/configuring-links.md index 147f564162d..a88348fa39c 100644 --- a/versioned_docs/version-6.x/configuring-links.md +++ b/versioned_docs/version-6.x/configuring-links.md @@ -63,7 +63,7 @@ const state = { }; ``` -By default, React Navigation will use the path segments as the route name when parsing the URL. But directly translating path segments to route names may not be the expected behavior, and your. +By default, React Navigation will use the path segments as the route name when parsing the URL. But directly translating path segments to route names may not be the expected behavior. For example, you might want to parse the path `/feed/latest` to something like: