Skip to content

Fix broken inline-code formatting in Data encoding lesson #5106

@matti-sarjala

Description

@matti-sarjala

URL to the relevant course

URL:
https://learning.quantum.ibm.com/course/quantum-machine-learning/data-encoding

Section / paragraph:
Learning course: “Data encoding”

Section:
“Introduction and notation”

Problem:
The paragraph says “like z_Feature Map and ZZ Feature Map)”. The inline-code formatting appears to be broken, and the feature-map names should likely be written as ZFeatureMapandZZFeatureMap`.

Select all that apply

  • new content request
  • typo
  • code bug
  • out-of-date content
  • broken link
  • other

Describe the fix or the content request.

In the Learning lesson Data encoding, there appears to be a small formatting/terminology typo in the Introduction and notation section.

The text currently says:

In practice, the built-in feature mappings in Qiskit (like `z_Feature Map and ZZ Feature Map) will typically include rotation layers and entangling layers...

The inline-code formatting appears to be broken: the backtick starts before z_Feature but does not close correctly.

I think this should likely be written as:

In practice, the built-in feature mappings in Qiskit, like ZFeatureMap and ZZFeatureMap, will typically include rotation layers and entangling layers...

Suggested minimal correction in learning/courses/quantum-machine-learning/data-encoding.ipynb:

- In practice, the built-in feature mappings in Qiskit (like `z_Feature Map and ZZ Feature Map) will typically include rotation layers and entangling layers that extend the state to many dimensions in the Hilbert space.
+ In practice, the built-in feature mappings in Qiskit, like `ZFeatureMap` and `ZZFeatureMap`, will typically include rotation layers and entangling layers that extend the state to many dimensions in the Hilbert space.

### For new content requests - if the request is accepted, do you want to write the content?

(No answer)

Metadata

Metadata

Type

No type

Projects

Status

No status

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions