From 4eb18bd3ad172e8dd370dcc0a92750f73a6e9a94 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=D0=90=D0=BB=D0=B5=D0=BA=D1=81=D0=B0=D0=BD=D0=B4=D1=8A?= =?UTF-8?q?=D1=80=20=D0=9A=D1=83=D1=80=D1=82=D0=B0=D0=BA=D0=BE=D0=B2?= Date: Thu, 18 Jun 2026 15:16:52 +0300 Subject: [PATCH] Fix typos in docs * Duplicate "the" * Enviroment - Environment --- .../guide/tools/editors/manifest_editor/access_rules.htm | 2 +- .../guide/tools/editors/manifest_editor/overview.htm | 2 +- .../guide/tools/editors/target_editor/environment_page.htm | 2 +- .../guide/tools/preference_pages/editors.htm | 2 +- .../reference/api-tooling/applications/analysis-application.htm | 2 +- .../tasks/pde_feature_generating_antcommandline.htm | 2 +- 6 files changed, 6 insertions(+), 6 deletions(-) diff --git a/org.eclipse.pde.doc.user/guide/tools/editors/manifest_editor/access_rules.htm b/org.eclipse.pde.doc.user/guide/tools/editors/manifest_editor/access_rules.htm index c0f4f3ee60c..8b3d6173dce 100644 --- a/org.eclipse.pde.doc.user/guide/tools/editors/manifest_editor/access_rules.htm +++ b/org.eclipse.pde.doc.user/guide/tools/editors/manifest_editor/access_rules.htm @@ -212,7 +212,7 @@

- In the example below, the the org.eclipse.pde.ui + In the example below, the org.eclipse.pde.ui friend plug-in has full access to the org.eclipse.pde.internal.core.bundle package from the org.eclipse.pde.core plug-in. diff --git a/org.eclipse.pde.doc.user/guide/tools/editors/manifest_editor/overview.htm b/org.eclipse.pde.doc.user/guide/tools/editors/manifest_editor/overview.htm index e63514dd3d3..4b16e052723 100644 --- a/org.eclipse.pde.doc.user/guide/tools/editors/manifest_editor/overview.htm +++ b/org.eclipse.pde.doc.user/guide/tools/editors/manifest_editor/overview.htm @@ -22,7 +22,7 @@

General Information

A Version is mandatory and must be of the form major.minor.micro.qualifier (e.g. 1.3.0).

A Name is the translatable presentation name of the plug-in. This field is required.

A Vendor is the translatable name of the plug-in vendor. This field is optional.

-

A Platform filter is a valid LDAP string that must evaluate to true in a running system for the the plug-in to run. For example, the following filter indicates that the plug-in is designed to only run on platforms with a win32 windowing system: Eclipse-PlatformFilter: (ws=win32). If a user attempts to run Eclipse on a platform that does not meet this requirement, the plug-in will be silently ignored by the runtime.

+

A Platform filter is a valid LDAP string that must evaluate to true in a running system for the plug-in to run. For example, the following filter indicates that the plug-in is designed to only run on platforms with a win32 windowing system: Eclipse-PlatformFilter: (ws=win32). If a user attempts to run Eclipse on a platform that does not meet this requirement, the plug-in will be silently ignored by the runtime.

An Activator is a Java class that controls the plug-in's life cycle. It is only needed if you require work to be done on the startup or shutdown of your plug-in.

Execution Environments

diff --git a/org.eclipse.pde.doc.user/guide/tools/editors/target_editor/environment_page.htm b/org.eclipse.pde.doc.user/guide/tools/editors/target_editor/environment_page.htm index c165cd0f5f9..cdb1db179e9 100755 --- a/org.eclipse.pde.doc.user/guide/tools/editors/target_editor/environment_page.htm +++ b/org.eclipse.pde.doc.user/guide/tools/editors/target_editor/environment_page.htm @@ -12,7 +12,7 @@

Environment Page

-

The Enviroment Page in the Target Definition Editor is used to edit many settings in the definition affecting how the target will be compiled and run.

+

The Environment Page in the Target Definition Editor is used to edit many settings in the definition affecting how the target will be compiled and run.

Environment Page diff --git a/org.eclipse.pde.doc.user/guide/tools/preference_pages/editors.htm b/org.eclipse.pde.doc.user/guide/tools/preference_pages/editors.htm index 6d1204fd7f0..4ca8d1af95e 100644 --- a/org.eclipse.pde.doc.user/guide/tools/preference_pages/editors.htm +++ b/org.eclipse.pde.doc.user/guide/tools/preference_pages/editors.htm @@ -20,7 +20,7 @@

Editors Preferences

XML Highlighting Preference

The XML Highlighting tab allows you to set the color and font for comments, constant strings, processing instructions, tags and text.

-

To customize the font and color for each element, select the element in the the left viewer and make changes using the buttons located on the right. The Preview pane automatically updates to reflect the changes you make.

+

To customize the font and color for each element, select the element in the left viewer and make changes using the buttons located on the right. The Preview pane automatically updates to reflect the changes you make.

This preference affects all plug-in development and user assistance editor source pages.

XML Syntax Highlighting

diff --git a/org.eclipse.pde.doc.user/reference/api-tooling/applications/analysis-application.htm b/org.eclipse.pde.doc.user/reference/api-tooling/applications/analysis-application.htm index e788fc25aa3..ec38403aca8 100644 --- a/org.eclipse.pde.doc.user/reference/api-tooling/applications/analysis-application.htm +++ b/org.eclipse.pde.doc.user/reference/api-tooling/applications/analysis-application.htm @@ -27,7 +27,7 @@

Application Arguments

project -This attribute specifies the location of the project to analyze. The project must be the a valid Eclipse Plugin project, +This attribute specifies the location of the project to analyze. The project must be a valid Eclipse Plugin project, that is a project with typical .project, MANIFEST.MF... files. Yes diff --git a/org.eclipse.pde.doc.user/tasks/pde_feature_generating_antcommandline.htm b/org.eclipse.pde.doc.user/tasks/pde_feature_generating_antcommandline.htm index 44dd8b49d7e..5dac9b331dd 100644 --- a/org.eclipse.pde.doc.user/tasks/pde_feature_generating_antcommandline.htm +++ b/org.eclipse.pde.doc.user/tasks/pde_feature_generating_antcommandline.htm @@ -353,7 +353,7 @@

Generating Ant scripts from the command line

Whether or not to use the resolver to verify that the provided plug-ins and features are -available.  This also determines whether or not the the feature +available.  This also determines whether or not the feature will be able to correctly handle platform specific fragments and plug-ins that will be JARed.  If all the elements to be included in the feature are available locally, then verify should be set to