Skip to content

Commit a7e92f2

Browse files
authored
fix xrefs using invalid format (OfficeDev#331)
1 parent c09e2f6 commit a7e92f2

11 files changed

+17
-17
lines changed

docs/general/how-to-add-a-new-document-part-that-receives-a-relationship-id-to-a-package.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,7 @@ It then adds the MainDocumentPart part in the new word processing document, with
5757
The code then adds the `DigitalSignatureOriginPart` part, the `ExtendedFilePropertiesPart` part, and the `ThumbnailPart` part in the new word processing document with realtionship IDs rId4, rId5, and rId6.
5858

5959
> [!NOTE]
60-
> The <xref:DocumentFormat.OpenXml.Packaging.WordprocessingDocument.AddNewPart*> method creates a relationship from the current document part to the new document part. This method returns the new document part. Also, you can use the <a href="xref:DocumentFormat.OpenXml.Packaging.DataPart.FeedData*?displayProperty=nameWithType"/> method to fill the document part.
60+
> The <xref:DocumentFormat.OpenXml.Packaging.WordprocessingDocument.AddNewPart*> method creates a relationship from the current document part to the new document part. This method returns the new document part. Also, you can use the <DocumentFormat.OpenXml.Packaging.DataPart.FeedData*> method to fill the document part.
6161
6262
## Sample Code
6363

docs/includes/presentation/structure.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -65,7 +65,7 @@ two slides denoted by the IDs 267 and 256.
6565

6666
Using the Open XML SDK, you can create document structure and
6767
content using strongly-typed classes that correspond to PresentationML
68-
elements. You can find these classes in the <a href="xref:DocumentFormat.OpenXml.Presentation?displayName=fullName" />
68+
elements. You can find these classes in the <xref:DocumentFormat.OpenXml.Presentation>
6969
namespace. The following table lists the class names of the classes that
7070
correspond to the `sld`, `sldLayout`, `sldMaster`, and `notesMaster` elements.
7171

docs/includes/word/structure.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ The basic document structure of a `WordProcessingML` document consists of the `d
1414
</w:document>
1515
```
1616

17-
Using the Open XML SDK, you can create document structure and content using strongly-typed classes that correspond to `WordprocessingML` elements. You will find these classes in the <a href="xref:DocumentFormat.OpenXml.Wordprocessing?displayProperty=fullName" /> namespace. The following table lists the class names of the classes that correspond to the `document`, `body`, `p`, `r`, and `t` elements.
17+
Using the Open XML SDK, you can create document structure and content using strongly-typed classes that correspond to `WordprocessingML` elements. You will find these classes in the <xref:DocumentFormat.OpenXml.Wordprocessing> namespace. The following table lists the class names of the classes that correspond to the `document`, `body`, `p`, `r`, and `t` elements.
1818

1919
| **WordprocessingML Element** | **Open XML SDK Class** | **Description** |
2020
|---|---|---|

docs/presentation/how-to-create-a-presentation-document-by-providing-a-file-name.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -69,7 +69,7 @@ slide layout, slide master, and theme parts.
6969

7070
Using the Open XML SDK, you can create presentation structure and
7171
content by using strongly-typed classes that correspond to
72-
PresentationML elements. You can find these classes in the <a href="xref:DocumentFormat.OpenXml.Presentation?displayName=fullName" />
72+
PresentationML elements. You can find these classes in the <xref:DocumentFormat.OpenXml.Presentation>
7373
namespace. The following table lists the names of the classes that
7474
correspond to the presentation, slide, slide master, slide layout, and
7575
theme elements. The class that corresponds to the theme element is

docs/presentation/structure-of-a-presentationml-document.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ A PresentationML document is not stored as one large body in a single part. Inst
2525

2626
## Important Presentation Parts
2727

28-
Using the Open XML SDK, you can create document structure and content that uses strongly-typed classes that correspond to PresentationML elements. You can find these classes in the <a href="xref:DocumentFormat.OpenXml.Presentation?displayName=fullName" /> namespace. The following table lists the class names of the classes that correspond to some of the important presentation elements.
28+
Using the Open XML SDK, you can create document structure and content that uses strongly-typed classes that correspond to PresentationML elements. You can find these classes in the <xref:DocumentFormat.OpenXml.Presentation> namespace. The following table lists the class names of the classes that correspond to some of the important presentation elements.
2929

3030
| **Package Part** | **Top Level PresentationML Element** | **Open XML SDK Class** | **Description**\* |
3131
|-------------------------|--------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

docs/presentation/working-with-handout-master-slides.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -143,7 +143,7 @@ turn, creates additional class instances: an instance of the <xref:DocumentForma
143143
instance of the <xref:DocumentFormat.OpenXml.Presentation.GroupShapeProperties> class, and an instance
144144
of the <xref:DocumentFormat.OpenXml.Presentation.Shape> class.
145145

146-
The namespace represented by the letter `P` in the code is the <a href="xref:DocumentFormat.OpenXml.Presentation?displayName=fullName" />
146+
The namespace represented by the letter `P` in the code is the <xref:DocumentFormat.OpenXml.Presentation>
147147
namespace.
148148

149149
### [C#](#tab/cs)

docs/presentation/working-with-notes-slides.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -168,7 +168,7 @@ the `CommonSlideData` class.
168168
--------------------------------------------------------------------------------
169169
## Open XML SDK Code Example
170170

171-
> In the following code snippets `P` represents the <a href="xref:DocumentFormat.OpenXml.Presentation?displayProperty=fullName"/> namespace and `D` represents the <a href="xref:DocumentFormat.OpenXml.Drawing?displayProperty=fullName"/> namespace.
171+
> In the following code snippets `P` represents the <xref:DocumentFormat.OpenXml.Presentation> namespace and `D` represents the <ref:DocumentFormat.OpenXml.Drawing> namespace.
172172
173173
In the snippet below, a presentation is opened with `Presentation.Open` and the first <xref:DocumentFormat.OpenXml.Packaging.SlidePart>
174174
is retrieved or added if the presentation does not already have a `SlidePart`.

docs/presentation/working-with-presentation-slides.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -51,7 +51,7 @@ In the above example the order specified to present the slides is slide
5151
4, then 3, 2, and finally 5.
5252

5353

54-
© [!include[ISO/IEC 29500 version](../includes/iso-iec-29500-version.md)]
54+
&copy; [!include[ISO/IEC 29500 version](../includes/iso-iec-29500-version.md)]
5555

5656
The `<sld/>` element is the root element of the PresentationML Slide
5757
part. For more information about the overall structure of the parts and
@@ -93,7 +93,7 @@ by the master is used. If the `<overrideClrMapping/>` child element is
9393
present, it defines a new color scheme specific to the parent notes
9494
slide, presentation slide, or slide layout.
9595

96-
© [!include[ISO/IEC 29500 version](../includes/iso-iec-29500-version.md)]
96+
&copy; [!include[ISO/IEC 29500 version](../includes/iso-iec-29500-version.md)]
9797

9898
### CommonSlideData Class
9999

@@ -112,7 +112,7 @@ The actual data in `<cSld/>` describe only the particular parent slide;
112112
it is only the type of information stored that is common across all
113113
slides.
114114

115-
© [!include[ISO/IEC 29500 version](../includes/iso-iec-29500-version.md)]
115+
&copy; [!include[ISO/IEC 29500 version](../includes/iso-iec-29500-version.md)]
116116

117117
### ExtensionListWithModification Class
118118

@@ -131,7 +131,7 @@ framework.
131131
[Note: Using this `extLst` element allows the generating application to
132132
store whether this extension property has been modified. end note]
133133

134-
© [!include[ISO/IEC 29500 version](../includes/iso-iec-29500-version.md)]
134+
&copy; [!include[ISO/IEC 29500 version](../includes/iso-iec-29500-version.md)]
135135

136136
### Timing Class
137137

@@ -146,7 +146,7 @@ More information on the specifics of these time nodes and how they are
146146
to be defined can be found within the Animation section of the
147147
PresentationML framework.
148148

149-
© [!include[ISO/IEC 29500 version](../includes/iso-iec-29500-version.md)]
149+
&copy; [!include[ISO/IEC 29500 version](../includes/iso-iec-29500-version.md)]
150150

151151
### Transition Class
152152

@@ -159,7 +159,7 @@ to transition to the current slide from the previous slide. That is, the
159159
transition information is stored on the slide that appears after the
160160
transition is complete.
161161

162-
© [!include[ISO/IEC 29500 version](../includes/iso-iec-29500-version.md)]
162+
&copy; [!include[ISO/IEC 29500 version](../includes/iso-iec-29500-version.md)]
163163

164164

165165
--------------------------------------------------------------------------------
@@ -195,7 +195,7 @@ All of these class instances and instances of the classes that represent
195195
the child elements of the `<sld/>` element are required to create the
196196
minimum number of XML elements necessary to represent a new slide.
197197

198-
The namespace represented by the letter *P* in the code is the <a href="xref:DocumentFormat.OpenXml.Presentation?displayName=fullName" />
198+
The namespace represented by the letter *P* in the code is the <xref:DocumentFormat.OpenXml.Presentation>
199199
namespace.
200200

201201
### [C#](#tab/cs-0)

docs/presentation/working-with-slide-layouts.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -168,7 +168,7 @@ the `CommonSlideData` class, the `ColorMapOverride` class, the <xref:DocumentFor
168168

169169
The following method from the article [How to: Create a presentation document by providing a file name](how-to-create-a-presentation-document-by-providing-a-file-name.md) adds a new slide layout part to an existing presentation and creates an instance of an Open XML SDK `SlideLayout` class in the new slide layout part. The `SlideLayout` class constructor creates instances of the `CommonSlideData` class and the `ColorMapOverride` class. The `CommonSlideData` class constructor creates an instance of the <xref:DocumentFormat.OpenXml.Presentation.ShapeTree> class, whose constructor in turn creates additional class instances: an instance of the <xref:DocumentFormat.OpenXml.Presentation.NonVisualGroupShapeProperties> class, an instance of the <xref:DocumentFormat.OpenXml.Presentation.GroupShapeProperties> class, and an instance of the <xref:DocumentFormat.OpenXml.Presentation.Shape> class.
170170

171-
The namespace represented by the letter *P* in the code is the <a href="xref:DocumentFormat.OpenXml.Presentation?displayName=fullName" /> namespace.
171+
The namespace represented by the letter *P* in the code is the <xref:DocumentFormat.OpenXml.Presentation> namespace.
172172

173173
### [C#](#tab/cs)
174174
[!code-csharp[](../../samples/presentation/create_by_providing_a_file_name/cs/Program.cs#snippet100)]

docs/presentation/working-with-slide-masters.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -147,7 +147,7 @@ element. Among these classes, as shown in the following code sample, are the `Co
147147

148148
The following method from the article [How to: Create a presentation document by providing a file name](./how-to-create-a-presentation-document-by-providing-a-file-name.md) adds a new slidemaster part to an existing presentation and creates an instance of an Open XML SDK `SlideMaster` class in the new slide master part. The `SlideMaster` class constructor creates instances of the `CommonSlideData` class and the `ColorMap`, `SlideLayoutIdList`, and `TextStyles` classes. The `CommonSlideData` class constructor creates an instance of the <xref:DocumentFormat.OpenXml.Presentation.ShapeTree> class, whose constructor in turn creates additional class instances: an instance of the <xref:DocumentFormat.OpenXml.Presentation.NonVisualGroupShapeProperties> class, an instance of the <xref:DocumentFormat.OpenXml.Presentation.GroupShapeProperties> class, and an instance of the <xref:DocumentFormat.OpenXml.Presentation.Shape> class, among others.
149149

150-
The namespace represented by the letter *P* in the code is the <a href="xref:DocumentFormat.OpenXml.Presentation?displayName=fullName" /> namespace.
150+
The namespace represented by the letter *P* in the code is the <xref:DocumentFormat.OpenXml.Presentation> namespace.
151151

152152
### [C#](#tab/cs)
153153
[!code-csharp[](../../samples/presentation/create_by_providing_a_file_name/cs/Program.cs#snippet99)]

0 commit comments

Comments
 (0)