Skip to main content
aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorWayne Beaton2020-07-07 01:51:46 +0000
committerWayne Beaton2020-07-07 01:51:46 +0000
commit9a53793f7125f18edba11b3f432ce255572589a4 (patch)
tree8a800316a865887a37a9b5a67be5802fff90c7c7
parent507f28d6b5e354bd002267384103965862afad30 (diff)
downloadorg.eclipse.dash.handbook-9a53793f7125f18edba11b3f432ce255572589a4.tar.gz
org.eclipse.dash.handbook-9a53793f7125f18edba11b3f432ce255572589a4.tar.xz
org.eclipse.dash.handbook-9a53793f7125f18edba11b3f432ce255572589a4.zip
Fix broken link syntax.
-rw-r--r--source/chapters/contributing.adoc2
-rw-r--r--source/chapters/ip.adoc4
2 files changed, 3 insertions, 3 deletions
diff --git a/source/chapters/contributing.adoc b/source/chapters/contributing.adoc
index 2737e3f..34facea 100644
--- a/source/chapters/contributing.adoc
+++ b/source/chapters/contributing.adoc
@@ -95,7 +95,7 @@ When a contributor becomes a committer, they must be covered by a committer agre
Eclipse Foundation project resources are accessible without an account. That is, members of the community may browse code, documentation, issues, help, etc. without creating an Eclipse Foundation Account. For those members of the community that wish to contribute code patches, open issues, add content to wikis, etc., an {accountUrl}[Eclipse Foundation Account] is required.
-For contributors and committers, their Eclipse Foundation account is their primary portal into their relationship with the Eclipse Foundation. From their account page, individuals can sign the <<contributing-eca, Eclipse Contributor Agreement>, manage their mailing list subscriptions, access build resources, and more.
+For contributors and committers, their Eclipse Foundation account is their primary portal into their relationship with the Eclipse Foundation. From their account page, individuals can sign the <<contributing-eca, Eclipse Contributor Agreement>>, manage their mailing list subscriptions, access build resources, and more.
[TIP]
====
diff --git a/source/chapters/ip.adoc b/source/chapters/ip.adoc
index b1bd42a..bfbaf5f 100644
--- a/source/chapters/ip.adoc
+++ b/source/chapters/ip.adoc
@@ -34,7 +34,7 @@ The ease with which software can be copied and combined makes it challenging to
____
In October 2019, The Eclipse Foundation's Board of Directors approved an update to the IP Policy that introduces several significant changes in our IP due diligence process.
-**License certification only for third-party content.** This change removes the requirement to perform deep copyright, provenance and scanning of anomalies for third-party content unless it is being modified and/or if there are _special_ considerations regarding the content. Instead, the focus for third-party content is on _license compatibility only, which had previously been referred to as _Type A_ due diligence.
+**License certification only for third-party content.** This change removes the requirement to perform deep copyright, provenance and scanning of anomalies for third-party content unless it is being modified and/or if there are _special_ considerations regarding the content. Instead, the focus for third-party content is on _license compatibility_ only, which had previously been referred to as _Type A_ due diligence.
**Leverage other sources of license information for third-party content.** With this change to license certification only for third-party content, we are able to leverage existing sources of information license information. That is, the requirement that the Eclipse IP Team personally review every bit of third-party content has been removed and we can now leverage other _trusted_ sources.
@@ -371,7 +371,7 @@ When content fails to meet these requirements, the project team must engage with
[TIP]
====
-The Eclipse Dash project's <ip-license-tool, IP License Tool>> will help you determine whether or not a CQ is required.
+The Eclipse Dash project's <<ip-license-tool, IP License Tool>> will help you determine whether or not a CQ is required.
====
When in doubt, committers should check with the Eclipse IP Team.

Back to the top